[Snyk] Fix for 1 vulnerabilities#5269
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 GuideUpgrade hard-coded versions of Backstage dependencies in the config-schema plugin to resolve a high-severity Improper Link Resolution vulnerability in tar-fs. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
⛔ Snyk checks have failed. 1 issues have been found so far.
⛔ security/snyk check is complete. 1 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "@backstage/config": "0.1.1", | ||
| "@backstage/core-components": "0.1.0", | ||
| "@backstage/core-plugin-api": "0.1.0", |
There was a problem hiding this comment.
This change replaces workspace references with pinned, very old versions (0.1.0/0.1.1) which could create compatibility issues with the rest of the Backstage ecosystem. The warning about the failed yarn.lock update further indicates potential dependency resolution problems.
Consider either:
- Using more recent versions that address the vulnerability but remain compatible with your codebase
- Maintaining the workspace references while addressing the
tar-fsvulnerability specifically (perhaps by adding a resolution in the root package.json)
Pinning to such early versions (0.1.x) is likely to break functionality as these predate many Backstage features and APIs.
| "@backstage/config": "0.1.1", | |
| "@backstage/core-components": "0.1.0", | |
| "@backstage/core-plugin-api": "0.1.0", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/core-components": "workspace:^", | |
| "@backstage/core-plugin-api": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
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.
|
|
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/config-schema/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: