-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Fix for 6 vulnerabilities #10431
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 addresses several security vulnerabilities detected in the project's yarn dependencies. It automates the process of upgrading specific packages to secure versions, thereby enhancing the overall security posture of the application. The changes primarily involve updating dependency versions in 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. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
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.
|
WalkthroughThis PR updates the dependency management strategy for the scaffolder-common plugin by replacing workspace protocol references with fixed version numbers. The changes affect two internal Backstage packages: Changes
Sequence DiagramThis diagram shows the interactions between components: sequenceDiagram
participant Dev as Developer
participant PM as Package Manager
participant Registry as NPM Registry
Note over Dev,Registry: Dependency Version Change (package.json)
Dev->>PM: Update package.json<br/>catalog-model: workspace:^ → 0.1.1<br/>types: workspace:^ → 0.1.1
Note over PM: Build/Install Process
alt Using workspace protocol (before)
PM->>PM: Resolve from local workspace
Note over PM: Uses local monorepo version
else Using fixed version (after)
PM->>Registry: Request @backstage/catalog-model@0.1.1
Registry-->>PM: Return package
PM->>Registry: Request @backstage/types@0.1.1
Registry-->>PM: Return package
Note over PM: Uses specific published versions
end
PM-->>Dev: Dependencies resolved
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. |
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 automated Snyk PR attempts to fix vulnerabilities by pinning dependencies, but the changes are incorrect for this monorepo's Yarn workspace structure. It replaces workspace:^ with fixed, outdated public versions, which will break internal package linking and likely cause build failures. For instance, @backstage/catalog-model is downgraded from workspace version 1.4.1 to 0.1.1. The failure to update yarn.lock, noted in the PR description, confirms the automated tool's incompatibility. I recommend rejecting this PR and addressing the vulnerabilities manually by updating the appropriate packages within the workspace.
| "@backstage/catalog-model": "0.1.1", | ||
| "@backstage/plugin-permission-common": "workspace:^", | ||
| "@backstage/types": "workspace:^" | ||
| "@backstage/types": "0.1.1" |
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.
Pinning @backstage/catalog-model and @backstage/types to specific versions is incorrect in this Yarn workspace setup. It breaks the monorepo's internal dependency linking, which relies on workspace:^. Furthermore, the pinned versions (0.1.1) are significant downgrades from the versions available in the workspace (@backstage/catalog-model is at 1.4.1, @backstage/types is at 1.1.0), which will almost certainly cause build failures and runtime errors. These dependencies should be reverted to use workspace:^.
| "@backstage/catalog-model": "0.1.1", | |
| "@backstage/plugin-permission-common": "workspace:^", | |
| "@backstage/types": "workspace:^" | |
| "@backstage/types": "0.1.1" | |
| "@backstage/catalog-model": "workspace:^", | |
| "@backstage/plugin-permission-common": "workspace:^", | |
| "@backstage/types": "workspace:^" |
Snyk has created this PR to fix 6 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/scaffolder-common/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
Updated dependency specifications in scaffolder-common plugin to support package publishing by replacing workspace protocol with fixed versions.
@backstage/catalog-modelfromworkspace:^to0.1.1@backstage/typesfromworkspace:^to0.1.1