Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 30, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/rollbar-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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  129  
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  45  

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:

🦉 Directory Traversal


EntelligenceAI PR Summary

This PR transitions the rollbar-backend plugin from workspace dependencies to pinned package versions.

  • Changed @backstage/backend-common from workspace:^ to explicit version 0.24.1
  • Changed @backstage/config from workspace:^ to explicit version 0.1.1
  • Indicates preparation for standalone package publishing or alignment with specific Backstage releases

@codesandbox
Copy link

codesandbox bot commented Jan 30, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

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 the resolution of critical security vulnerabilities within the project's yarn dependencies. By updating specific Backstage core dependencies, it aims to mitigate known risks, ensuring the application remains secure against potential exploits like directory traversal and uncontrolled recursion.

Highlights

  • Security Vulnerability Fixes: This PR, automatically generated by Snyk, addresses three medium-severity vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
  • Dependency Updates: The plugins/rollbar-backend/package.json file has been updated to upgrade @backstage/backend-common from workspace:^ to 0.24.1 and @backstage/config from workspace:^ to 0.1.1.
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.

@snyk-io
Copy link

snyk-io bot commented Jan 30, 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.

@socket-security
Copy link

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

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

Copy link

@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 in plugins/rollbar-backend/package.json. However, the proposed change replaces workspace:^ versioning with pinned versions for @backstage/backend-common and @backstage/config. This is a significant issue in a monorepo setup as it breaks the workspace protocol, potentially leading to dependency conflicts and build failures. My review includes a critical comment explaining why this approach is incorrect and suggests reverting the change. The vulnerabilities should be addressed by updating the dependencies at the root of the monorepo.

Comment on lines +36 to +37
"@backstage/backend-common": "0.24.1",
"@backstage/config": "0.1.1",

Choose a reason for hiding this comment

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

critical

Pinning the versions of @backstage/backend-common and @backstage/config breaks the yarn workspace convention used in this monorepo. The workspace:^ protocol is essential for maintaining dependency consistency across all packages in the workspace.

While the intent to fix vulnerabilities is correct, this approach of pinning versions in a sub-package is incorrect for a monorepo and will likely cause issues, such as:

  • Multiple versions of the same package being installed.
  • Incompatibilities with other packages that expect the workspace version.
  • Breaking the build or causing runtime errors.

The correct way to resolve these vulnerabilities is to update the dependencies at the root of the monorepo and then run yarn to update the yarn.lock file. This ensures the fix is applied consistently across the entire project.

It is strongly recommended to revert these changes and address the vulnerabilities at the monorepo level.

    "@backstage/backend-common": "workspace:^",
    "@backstage/config": "workspace:^"

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management strategy for the rollbar-backend plugin by replacing workspace protocol references with explicit version numbers. The changes affect two core Backstage packages: @backstage/backend-common is pinned to version 0.24.1, and @backstage/config is pinned to version 0.1.1. This transition from monorepo workspace dependencies (workspace:^) to fixed version specifications suggests the plugin is being prepared for standalone distribution or needs to align with specific Backstage release versions for compatibility purposes.

Changes

File(s) Summary
plugins/rollbar-backend/package.json Updated dependency specifications from workspace protocol (workspace:^) to explicit versions: @backstage/backend-common to 0.24.1 and @backstage/config to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant RB as Rollbar Backend Plugin
    participant BC as @backstage/backend-common
    participant C as @backstage/config
    
    Note over RB,C: Dependency Version Update
    
    Note over RB: Before: Uses workspace protocol
    RB->>BC: depends on workspace:^
    RB->>C: depends on workspace:^
    
    Note over RB,C: ---
    
    Note over RB: After: Uses pinned versions
    RB->>BC: depends on 0.24.1
    RB->>C: depends on 0.1.1
    
    Note over RB,C: Change from monorepo workspace<br/>references to explicit npm versions
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.

3 participants