Skip to content

[Snyk] Fix for 2 vulnerabilities#11870

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-39f6b4f2bf8a3ab852c26044e45767ca
Open

[Snyk] Fix for 2 vulnerabilities#11870
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-39f6b4f2bf8a3ab852c26044e45767ca

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Feb 7, 2026

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • packages/dev-utils/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  380  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  380  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR pins Backstage dependencies in the dev-utils package to specific versions instead of using workspace protocol.

  • Changed @backstage/core-components from workspace protocol to fixed version 0.1.0
  • Changed @backstage/integration-react from workspace protocol to fixed version 0.1.1
  • Changed @backstage/plugin-catalog-react from workspace protocol to fixed version 0.0.1
  • Modified dependency specifications in packages/dev-utils/package.json

@codesandbox
Copy link

codesandbox bot commented Feb 7, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Author

snyk-io bot commented Feb 7, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@socket-security
Copy link

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.8.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management strategy for the dev-utils package by replacing workspace protocol references with fixed version numbers for three Backstage dependencies. The changes pin @backstage/core-components to version 0.1.0, @backstage/integration-react to version 0.1.1, and @backstage/plugin-catalog-react to version 0.0.1. This modification moves away from monorepo workspace resolution to explicit version pinning, which typically indicates preparation for package publishing, testing with specific dependency versions, or establishing a stable dependency baseline for the dev-utils package.

Changes

File(s) Summary
packages/dev-utils/package.json Updated three Backstage dependencies from workspace protocol to fixed versions: @backstage/core-components to 0.1.0, @backstage/integration-react to 0.1.1, and @backstage/plugin-catalog-react to 0.0.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant DevUtils as @backstage/dev-utils
    participant CoreComp as @backstage/core-components
    participant IntReact as @backstage/integration-react
    participant CatReact as @backstage/plugin-catalog-react

    Note over PM,CatReact: Dependency Resolution Change

    PM->>DevUtils: Read package.json
    Note over DevUtils: Dependencies changed from<br/>workspace:^ to fixed versions

    alt Before Change (workspace:^)
        DevUtils->>CoreComp: Link to local workspace version
        DevUtils->>IntReact: Link to local workspace version
        DevUtils->>CatReact: Link to local workspace version
        Note over DevUtils,CatReact: Uses local development versions
    else After Change (fixed versions)
        PM->>CoreComp: Resolve @backstage/core-components@0.1.0
        CoreComp-->>PM: Return published package
        PM->>IntReact: Resolve @backstage/integration-react@0.1.1
        IntReact-->>PM: Return published package
        PM->>CatReact: Resolve @backstage/plugin-catalog-react@0.0.1
        CatReact-->>PM: Return published package
        Note over PM,CatReact: Uses published registry versions
    end

    PM->>DevUtils: Install resolved dependencies
    DevUtils-->>PM: Dependencies installed

    Note over DevUtils: Package ready with<br/>fixed version dependencies
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants