[Snyk] Security upgrade @backstage/backend-plugin-api from 0.0.0-use.local to 0.6.19#5390
[Snyk] Security upgrade @backstage/backend-plugin-api from 0.0.0-use.local to 0.6.19#5390
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-10293725
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuidePins the @backstage/backend-plugin-api dependency in the events-node plugin to v0.6.19 to remediate a high-severity tarFS vulnerability; note that the lockfile wasn’t updated by Snyk and must be regenerated manually. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
|
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.
|
| }, | ||
| "dependencies": { | ||
| "@backstage/backend-plugin-api": "workspace:^" | ||
| "@backstage/backend-plugin-api": "0.6.19" |
There was a problem hiding this comment.
This change from workspace:^ to a fixed version 0.6.19 breaks the monorepo's workspace dependency structure. In Backstage monorepos, workspace references ensure all internal packages use consistent versions during development.
The failed yarn.lock update mentioned in the PR description confirms there are compatibility issues with this approach.
To properly address the security vulnerability:
- Maintain the
workspace:^format - Update the vulnerable dependency at the root level
- Ensure the fix propagates through the workspace
This ensures the security fix is applied while preserving the monorepo's integrity and version consistency across all packages.
| "@backstage/backend-plugin-api": "0.6.19" | |
| "@backstage/backend-plugin-api": "workspace:^" |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
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! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/events-node/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-TARFS-10293725
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:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Bug Fixes: