Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 25, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/badges-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 Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  208  
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  146  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  113  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  88  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  88  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  62  

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution


EntelligenceAI PR Summary

This PR updates dependency versions in the badges-backend plugin, moving from workspace protocol to pinned versions for core Backstage packages and upgrading lodash for security.

  • Updated @backstage/backend-common to 0.25.0
  • Updated @backstage/backend-plugin-api to 1.6.1
  • Updated @backstage/catalog-model to 0.1.1
  • Updated @backstage/plugin-auth-node to 0.6.0
  • Upgraded lodash from ^4.17.21 to ^4.17.23 for security patches
  • Transitioned from workspace protocol references to explicit version pinning for core dependencies

@codesandbox
Copy link

codesandbox bot commented Jan 25, 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, automatically generated by Snyk, focuses on enhancing the project's security by updating several key dependencies within the 'plugins/badges-backend/package.json' file. The changes specifically target and resolve six identified vulnerabilities across various packages, aiming to mitigate potential security risks and maintain a robust and secure codebase.

Highlights

  • Dependency Updates: Several @backstage packages (@backstage/backend-common, @backstage/backend-plugin-api, @backstage/catalog-model, @backstage/plugin-auth-node) have been updated from 'workspace:^' to specific versions ('0.25.0', '1.6.1', '0.1.1', '0.6.0' respectively).
  • Lodash Version Bump: The 'lodash' dependency has been upgraded from '^4.17.21' to '^4.17.23'.
  • Vulnerability Fixes: These dependency updates are intended to fix 6 identified vulnerabilities, including issues related to Unicode Encoding, Cryptographic Primitive implementation, Symlink Following, Prototype Pollution, and Regular Expression Denial of Service (ReDoS).
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 25, 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.

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 from Snyk aims to resolve 6 security vulnerabilities by updating dependencies in plugins/badges-backend/package.json. While addressing security issues is important, there are two major concerns with this PR. First and most critically, the yarn.lock file has not been updated, as noted in the pull request description. This means the dependency changes will not be applied, and the vulnerabilities will persist. You must run yarn install and commit the updated yarn.lock file before merging. Second, this PR changes several @backstage dependencies from workspace:^ to pinned versions. This is a significant change that can lead to dependency conflicts or subtle runtime issues within the monorepo by causing multiple versions of framework packages to be installed. This approach seems inconsistent as other workspace dependencies are not pinned. Please carefully evaluate if this is the desired long-term solution or if the vulnerabilities can be addressed by updating the packages within the workspace.

Comment on lines +36 to +42
"@backstage/backend-common": "0.25.0",
"@backstage/backend-plugin-api": "1.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-auth-node": "0.6.0",

Choose a reason for hiding this comment

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

high

This PR pins several @backstage dependencies to specific versions instead of using workspace:^. This is a significant change for a package within a monorepo because it opts out of using the local workspace versions of these packages. This can lead to installing multiple versions of the same framework packages, potentially causing subtle runtime bugs (e.g., with instanceof checks or singletons).

This change is also inconsistent, as other @backstage dependencies (e.g., @backstage/catalog-client) remain on workspace:^.

While this may resolve the reported vulnerabilities, please verify if this is the intended approach. A better solution might be to upgrade the packages across the entire workspace to resolve the transitive vulnerabilities while maintaining the integrity of the monorepo structure.

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates dependency management in the badges-backend plugin by transitioning from workspace protocol references to pinned versions for core Backstage packages. The changes include upgrading @backstage/backend-common to 0.25.0, @backstage/backend-plugin-api to 1.6.1, @backstage/catalog-model to 0.1.1, and @backstage/plugin-auth-node to 0.6.0. Additionally, the lodash dependency is upgraded from ^4.17.21 to ^4.17.23 to incorporate security patches. This shift towards explicit version management improves dependency stability and security while maintaining workspace protocol for other internal packages.

Changes

File(s) Summary
plugins/badges-backend/package.json Transitioned core Backstage dependencies from workspace protocol to pinned versions (@backstage/backend-common@0.25.0, @backstage/backend-plugin-api@1.6.1, @backstage/catalog-model@0.1.1, @backstage/plugin-auth-node@0.6.0) and upgraded lodash from ^4.17.21 to ^4.17.23 for security patches.

▶️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