-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Fix for 6 vulnerabilities #10750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TAR-15038581 - https://snyk.io/vuln/SNYK-JS-ELLIPTIC-14908844 - https://snyk.io/vuln/SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291 - https://snyk.io/vuln/SNYK-JS-LODASH-15053838 - https://snyk.io/vuln/SNYK-JS-LODASHES-15053836 - https://snyk.io/vuln/SNYK-JS-DIFF-14917201
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Summary of ChangesHello @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
Using Gemini Code AssistThe 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
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 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
|
⛔ Snyk checks have failed. 1 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
There was a problem hiding this 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.
| "@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", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
WalkthroughThis 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
Note for WindsurfPlease 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 belowEmoji Descriptions:
Interact with the Bot:
Also you can trigger various commands with the bot by doing The current supported commands are
More commands to be added soon. |
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.jsonNote 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 runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TAR-15038581
SNYK-JS-ELLIPTIC-14908844
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
SNYK-JS-LODASH-15053838
SNYK-JS-LODASHES-15053836
SNYK-JS-DIFF-14917201
Important
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.