Skip to content

[Snyk] Fix for 2 vulnerabilities#11816

Closed
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-7ce93ba367612a45a3acf998f3c95e0d
Closed

[Snyk] Fix for 2 vulnerabilities#11816
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-7ce93ba367612a45a3acf998f3c95e0d

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 6, 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):

  • plugins/scaffolder-backend-module-sentry/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
  84  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  84  

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 transitions the Sentry scaffolder backend module from workspace-based dependency management to fixed version pinning for Backstage packages.

  • Changed @backstage/config from workspace:^ to 0.1.1
  • Changed @backstage/errors from workspace:^ to 0.1.1
  • Changed @backstage/plugin-scaffolder-node from workspace:^ to 0.2.0
  • Indicates preparation for package release or distribution outside monorepo workspace

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 6, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the project by resolving two critical Server-side Request Forgery (SSRF) vulnerabilities. This is achieved through targeted updates to several @backstage dependencies within the plugins/scaffolder-backend-module-sentry package, ensuring the application benefits from the latest security patches and improved stability.

Highlights

  • Vulnerability Fixes: This pull request addresses and fixes two Server-side Request Forgery (SSRF) vulnerabilities (SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969) identified by Snyk.
  • Dependency Upgrades: The @backstage/config dependency has been upgraded from workspace:^ to 0.1.1.
  • Dependency Upgrades: The @backstage/errors dependency has been upgraded from workspace:^ to 0.1.1.
  • Dependency Upgrades: The @backstage/plugin-scaffolder-node dependency has been upgraded from workspace:^ to 0.2.0.
Changelog
  • plugins/scaffolder-backend-module-sentry/package.json
    • Updated @backstage/config dependency from workspace:^ to 0.1.1.
    • Updated @backstage/errors dependency from workspace:^ to 0.1.1.
    • Updated @backstage/plugin-scaffolder-node dependency from workspace:^ to 0.2.0.
Activity
  • This pull request was automatically created by Snyk to address and fix identified vulnerabilities.
  • The PR specifically targets two Server-side Request Forgery (SSRF) vulnerabilities.
  • A warning is present indicating that the yarn.lock file failed to update and requires manual intervention.
  • Snyk has provided links to view the latest project report, customize PR templates, adjust project settings, and understand Snyk's upgrade logic.
  • Interactive lessons on Server-side Request Forgery (SSRF) are also linked for further learning.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 6, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedreact@​17.0.21001007897100
Addedstorybook-dark-mode@​1.1.29910010080100
Addedswc-loader@​0.2.31001009285100
Addedreact-hot-loader@​4.13.19710010085100
Addedtypescript@​4.7.410010010010080
Addedreact-dom@​17.0.21001009098100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 6, 2026

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 polished under OFL-1.1

License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/docs/assets/fonts/LICENSE.txt)

From: ?npm/@storybook/addon-actions@6.5.16npm/polished@4.2.2

ℹ 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/polished@4.2.2. 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.

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: storybook/package.jsonnpm/typescript@4.7.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.7.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

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 6, 2026

Snyk checks have passed. No issues have been found so far.

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

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

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR updates dependency management for the Sentry scaffolder backend module by replacing workspace protocol references with explicit version numbers. Three Backstage packages are affected: @backstage/config and @backstage/errors are pinned to version 0.1.1, while @backstage/plugin-scaffolder-node is pinned to version 0.2.0. This transition from workspace:^ to fixed versions suggests the package is being prepared for independent distribution or release outside of a monorepo workspace environment, ensuring consistent dependency resolution for external consumers.

Changes

File(s) Summary
plugins/scaffolder-backend-module-sentry/package.json Updated three Backstage package dependencies from workspace protocol (workspace:^) to explicit versions: @backstage/config and @backstage/errors to 0.1.1, and @backstage/plugin-scaffolder-node to 0.2.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant PKG as scaffolder-backend-module-sentry
    participant DEP as Backstage Dependencies

    Note over PM,DEP: Dependency Resolution Change
    
    PM->>PKG: Install dependencies
    
    Note over PKG: Previously: workspace:^ references<br/>Now: Fixed versions
    
    PKG->>DEP: Request @backstage/config@0.1.1
    DEP-->>PKG: Return config module
    
    PKG->>DEP: Request @backstage/errors@0.1.1
    DEP-->>PKG: Return errors module
    
    PKG->>DEP: Request @backstage/plugin-scaffolder-node@0.2.0
    DEP-->>PKG: Return scaffolder-node module
    
    PKG-->>PM: Dependencies resolved
    
    Note over PM,DEP: No runtime behavior changes<br/>Only dependency version pinning
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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by updating dependencies. However, the proposed changes incorrectly downgrade several core @backstage packages by replacing workspace:^ versions with old, pinned versions. This is a critical issue that will likely break the build or cause runtime errors. The changes should be reverted, and the vulnerability should be addressed without these incorrect downgrades.

Comment on lines +25 to +27
"@backstage/config": "0.1.1",
"@backstage/errors": "0.1.1",
"@backstage/plugin-scaffolder-node": "0.2.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This change incorrectly downgrades several dependencies. The workspace:^ protocol is used in this monorepo to refer to other packages within the same repository. By replacing it with pinned, old versions, you are introducing significant downgrades:

  • @backstage/config is downgraded from a workspace version (which is 1.0.8 in this repository) to 0.1.1.
  • @backstage/errors is downgraded from a workspace version (which is 1.2.1 in this repository) to 0.1.1.

This will almost certainly break the application. These changes should be reverted. The Snyk bot seems to have misinterpreted the workspace: protocol. The underlying vulnerability should be addressed without downgrading these packages. Furthermore, the PR description warns that yarn.lock failed to update, which is another strong indicator that these changes are problematic.

Suggested change
"@backstage/config": "0.1.1",
"@backstage/errors": "0.1.1",
"@backstage/plugin-scaffolder-node": "0.2.0"
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-scaffolder-node": "workspace:^"

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 13, 2026
@github-actions github-actions Bot closed this Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants