[Snyk] Fix for 1 vulnerabilities#5408
Conversation
…abilities 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 GuideThis PR pins three Backstage dependencies in the embedded TechDocs CLI app from workspace ranges to fixed versions to resolve a high-severity path traversal vulnerability in tar-fs. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
⛔ Snyk checks have failed. 2 issues have been found so far.
⛔ security/snyk check is complete. 2 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
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.
|
| "@backstage/core-components": "0.1.0", | ||
| "@backstage/core-plugin-api": "workspace:^", | ||
| "@backstage/integration-react": "workspace:^", | ||
| "@backstage/integration-react": "0.1.1", | ||
| "@backstage/plugin-catalog": "workspace:^", | ||
| "@backstage/plugin-techdocs": "workspace:^", | ||
| "@backstage/plugin-techdocs": "0.1.1", |
There was a problem hiding this comment.
This change introduces dependency management inconsistency by replacing workspace:^ references with fixed, outdated versions (0.1.0, 0.1.1). In a monorepo, mixing workspace references with pinned versions disrupts the dependency resolution system and can create compatibility issues with other packages that continue using workspace references.
The warning in the PR description ("Failed to update the yarn.lock") further indicates that this approach may not properly resolve the security vulnerability.
A more appropriate solution would be to maintain the workspace:^ references while updating the vulnerable dependencies at their source within the monorepo. This preserves the integrity of the workspace dependency model while addressing the security concern.
| "@backstage/core-components": "0.1.0", | |
| "@backstage/core-plugin-api": "workspace:^", | |
| "@backstage/integration-react": "workspace:^", | |
| "@backstage/integration-react": "0.1.1", | |
| "@backstage/plugin-catalog": "workspace:^", | |
| "@backstage/plugin-techdocs": "workspace:^", | |
| "@backstage/plugin-techdocs": "0.1.1", | |
| "@backstage/core-components": "workspace:^", | |
| "@backstage/core-plugin-api": "workspace:^", | |
| "@backstage/integration-react": "workspace:^", | |
| "@backstage/plugin-catalog": "workspace:^", | |
| "@backstage/plugin-techdocs": "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):
packages/techdocs-cli-embedded-app/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
Upgrade backstage dependencies in techdocs-cli-embedded-app to released versions to fix a high severity tar-fs vulnerability.
Bug Fixes:
Enhancements: