Skip to content

[Snyk] Security upgrade @backstage/config from 0.0.0-use.local to 0.1.1#11814

Closed
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-6dbbab3ced80ce1bbc95f438f22d1301
Closed

[Snyk] Security upgrade @backstage/config from 0.0.0-use.local to 0.1.1#11814
q1blue wants to merge 2 commits intomasterfrom
snyk-fix-6dbbab3ced80ce1bbc95f438f22d1301

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/airbrake-backend/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 locks the @backstage/config dependency to a specific version in the airbrake-backend plugin.

  • Replaced workspace reference (workspace:^) with pinned version 0.1.1
  • Modified dependency declaration in plugins/airbrake-backend/package.json
  • Ensures consistent version resolution across different build and installation environments
  • May indicate preparation for publishing or resolution of workspace dependency issues

@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 automates a crucial security update for the @backstage/config package within the airbrake-backend plugin. By bumping the dependency version, it directly mitigates known Server-side Request Forgery vulnerabilities, enhancing the overall security of the application. Reviewers should pay close attention to the manual yarn.lock update requirement to ensure a smooth integration.

Highlights

  • Security Upgrade: This pull request, automatically generated by Snyk, upgrades the @backstage/config dependency from workspace:^ to 0.1.1 in plugins/airbrake-backend/package.json.
  • Vulnerability Fixes: The upgrade addresses two Server-side Request Forgery (SSRF) vulnerabilities (SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969) with a severity score of 84.
  • Manual Intervention Required: A warning indicates that yarn.lock was not automatically updated and requires manual intervention before merging, especially for projects using Yarn's zero-installs feature.
Changelog
  • plugins/airbrake-backend/package.json
    • Updated @backstage/config dependency from workspace:^ to 0.1.1.
Activity
  • Snyk automatically created this pull request to address security vulnerabilities.
  • The PR identifies two Server-side Request Forgery (SSRF) vulnerabilities that will be fixed by the upgrade.
  • A warning has been issued regarding the failure to update yarn.lock, requiring manual action.
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.

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

Walkthrough

This PR updates the dependency management configuration for the airbrake-backend plugin by changing the @backstage/config package from a workspace reference to a pinned version. The modification replaces the flexible workspace protocol (workspace:^) with a specific locked version (0.1.1), which ensures version stability and predictable behavior across different environments. This change likely supports preparation for package publishing, resolves workspace dependency conflicts, or enforces stricter version control for the config package dependency.

Changes

File(s) Summary
plugins/airbrake-backend/package.json Changed @backstage/config dependency from workspace reference (workspace:^) to pinned version (0.1.1) for version stability.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant AB as airbrake-backend Plugin
    participant WS as Workspace
    participant NPM as NPM Registry
    
    Note over PM,NPM: Before: workspace:^ dependency
    PM->>AB: Resolve dependencies
    AB->>PM: Request @backstage/config
    PM->>WS: Resolve from local workspace
    WS-->>PM: Return local package
    PM-->>AB: Link local @backstage/config
    
    Note over PM,NPM: After: 0.1.1 specific version
    PM->>AB: Resolve dependencies
    AB->>PM: Request @backstage/config@0.1.1
    PM->>NPM: Fetch @backstage/config@0.1.1
    NPM-->>PM: Return published package
    PM-->>AB: Install @backstage/config@0.1.1
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.

@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.

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 automated Snyk pull request attempts to resolve a security vulnerability by modifying the @backstage/config dependency. However, the proposed change from workspace:^ to a hardcoded version 0.1.1 is incorrect for this monorepo structure. This change represents a significant downgrade from the workspace version (1.0.8) and will almost certainly lead to build failures or runtime errors due to type conflicts. I have added a comment recommending to revert this change. The proper way to fix the vulnerability would be to update the @backstage/config package itself within the workspace, not by pinning an old version in a downstream package.

"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config": "0.1.1",
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 introduces a critical issue by pinning @backstage/config to version 0.1.1, while other packages in this monorepo use workspace:^ to resolve to the workspace version, which is 1.0.8.

This downgrade will cause two different versions of @backstage/config to be installed, leading to type incompatibilities that will likely break the build or cause runtime errors. For example, the airbrakePlugin receives a config object from coreServices (which uses @backstage/config@1.0.8) and passes it to extractAirbrakeConfig, which expects a Config type from @backstage/config@0.1.1.

To maintain consistency and prevent these issues, this dependency should continue to use the version from the workspace.

Suggested change
"@backstage/config": "0.1.1",
"@backstage/config": "workspace:^",

@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 atob under CC-BY-3.0

License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS)

From: ?npm/atob@2.1.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/atob@2.1.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.

View full report

@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 14, 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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants