[Snyk] Fix for 4 vulnerabilities by snyk-io[bot] · Pull Request #5587 · https-quantumblockchainai-atlassian-net/backstage

snyk-io · 2025-06-05T08:18:03Z

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

plugins/todo-backend/package.json

Note 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 run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️

Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Origin Validation Error SNYK-JS-WEBPACKDEVSERVER-10300775	748
	Uncaught Exception SNYK-JS-MULTER-10299078	746
	Improper Link Resolution Before File Access ('Link Following') SNYK-JS-TARFS-10293725	721
	Exposed Dangerous Method or Function SNYK-JS-WEBPACKDEVSERVER-10300777	693

Important

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Uncaught Exception
🦉 Improper Link Resolution Before File Access ('Link Following')

Summary by Sourcery

Bug Fixes:

Upgrade @backstage/backend-common, @backstage/backend-openapi-utils, @backstage/catalog-client, @backstage/catalog-model, and @backstage/plugin-catalog-node to specific released versions to resolve Snyk-reported vulnerabilities

The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300775 - https://snyk.io/vuln/SNYK-JS-MULTER-10299078 - https://snyk.io/vuln/SNYK-JS-TARFS-10293725 - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300777

codesandbox · 2025-06-05T08:18:07Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

sourcery-ai · 2025-06-05T08:18:08Z

Reviewer's Guide

This PR fixes four vulnerabilities by replacing workspace-based dependencies in the todo-backend plugin’s package.json with fixed version releases, ensuring patched versions of Backstage packages are installed.

File-Level Changes

Change	Details	Files
Pinned backend utility dependencies to specific secure versions	Replaced workspace:^ with 0.24.1 for backend-common Replaced workspace:^ with 0.0.1 for backend-openapi-utils	`plugins/todo-backend/package.json`
Updated catalog client and model packages to patched releases	Replaced workspace:^ with 0.2.0 for catalog-client Replaced workspace:^ with 0.1.1 for catalog-model	`plugins/todo-backend/package.json`
Locked plugin-catalog-node to a stable release	Replaced workspace:^ with 1.0.0 for plugin-catalog-node	`plugins/todo-backend/package.json`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

graphite-app · 2025-06-05T08:19:29Z

+    "@backstage/backend-common": "0.24.1",
+    "@backstage/backend-openapi-utils": "0.0.1",
    "@backstage/backend-plugin-api": "workspace:^",
-    "@backstage/catalog-client": "workspace:^",
-    "@backstage/catalog-model": "workspace:^",
+    "@backstage/catalog-client": "0.2.0",
+    "@backstage/catalog-model": "0.1.1",
    "@backstage/config": "workspace:^",
    "@backstage/errors": "workspace:^",
    "@backstage/integration": "workspace:^",
-    "@backstage/plugin-catalog-node": "workspace:^",
+    "@backstage/plugin-catalog-node": "1.0.0",


This PR introduces inconsistent dependency management by mixing specific version numbers with workspace references (workspace:^). In a monorepo architecture, this approach can lead to version conflicts and dependency resolution issues.

The change converts some dependencies to fixed versions:

"@backstage/backend-common": "0.24.1", "@backstage/backend-openapi-utils": "0.0.1", "@backstage/catalog-client": "0.2.0", "@backstage/catalog-model": "0.1.1", "@backstage/plugin-catalog-node": "1.0.0",

While leaving others as workspace references:

"@backstage/backend-plugin-api": "workspace:^", "@backstage/config": "workspace:^", "@backstage/errors": "workspace:^", "@backstage/integration": "workspace:^",

For monorepo stability, consider either:

Keeping all Backstage dependencies as workspace references

Converting all Backstage dependencies to specific versions

This ensures consistent dependency resolution throughout the project.

Suggested change

"@backstage/backend-common": "0.24.1",

"@backstage/backend-openapi-utils": "0.0.1",

"@backstage/backend-plugin-api": "workspace:^",

"@backstage/catalog-client": "workspace:^",

"@backstage/catalog-model": "workspace:^",

"@backstage/catalog-client": "0.2.0",

"@backstage/catalog-model": "0.1.1",

"@backstage/config": "workspace:^",

"@backstage/errors": "workspace:^",

"@backstage/integration": "workspace:^",

"@backstage/plugin-catalog-node": "workspace:^",

"@backstage/plugin-catalog-node": "1.0.0",

"@backstage/backend-common": "workspace:^",

"@backstage/backend-openapi-utils": "workspace:^",

"@backstage/backend-plugin-api": "workspace:^",

"@backstage/catalog-client": "workspace:^",

"@backstage/catalog-model": "workspace:^",

"@backstage/config": "workspace:^",

"@backstage/errors": "workspace:^",

"@backstage/integration": "workspace:^",

"@backstage/plugin-catalog-node": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

socket-security · 2025-06-05T08:19:33Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Quality
	@swc/core-darwin-arm64@1.3.68
	@swc/core-darwin-x64@1.3.68
	@swc/core-linux-arm-gnueabihf@1.3.68
	@swc/core-linux-arm64-gnu@1.3.68
	@swc/core-linux-arm64-musl@1.3.68
	@swc/core-linux-x64-gnu@1.3.68
	@swc/core-linux-x64-musl@1.3.68
	@swc/core-win32-arm64-msvc@1.3.68
	@swc/core-win32-ia32-msvc@1.3.68
	@swc/core-win32-x64-msvc@1.3.68
	has@1.0.3
	isarray@2.0.5
	has-proto@1.0.1
	array-buffer-byte-length@1.0.0
	gopd@1.2.0 ⏵ 1.0.1	^-1
	node-releases@2.0.6
	globalthis@1.0.3
	has-property-descriptors@1.0.0
	has-tostringtag@1.0.0
	is-weakmap@2.0.1
	define-properties@1.2.0
	functions-have-names@1.2.3
	es-get-iterator@1.1.3
	aggregate-error@3.1.0
	object.fromentries@2.0.5
See 649 more rows in the dashboard

View full report

socket-security · 2025-06-05T08:19:34Z

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.

Action	Severity	Alert (click for details)
Warn		`@babel/traverse@7.18.11` has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: yarn.lock → `npm/@babel/helper-module-transforms@7.18.9` → `npm/@babel/traverse@7.18.11` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@babel/traverse@7.18.11`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`atob@2.1.2` has a License Policy Violation. License: CC-BY-3.0 (package/LICENSE.DOCS) From: storybook/yarn.lock → `npm/atob@2.1.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/atob@2.1.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`caniuse-lite@1.0.30001378` has a License Policy Violation. License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: yarn.lock → `npm/caniuse-lite@1.0.30001378` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001378`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`polished@4.2.2` has a License Policy Violation. License: OFL-1.1 (package/docs/assets/fonts/LICENSE.txt) From: storybook/yarn.lock → `npm/polished@4.2.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/polished@4.2.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

snyk-io · 2025-06-05T10:54:53Z

⛔ Snyk checks have failed. 1 issues have been found so far.

Icon	Severity	Issues
	Critical	0
	High	0
	Medium	1
	Low	0

⛔ 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.

github-actions · 2025-06-12T10:55:12Z

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!

graphite-app Bot reviewed Jun 5, 2025

View reviewed changes

github-actions Bot added the stale label Jun 12, 2025

github-actions Bot closed this Jun 17, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Fix for 4 vulnerabilities#5587

[Snyk] Fix for 4 vulnerabilities#5587
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-eb3cd5729d38b8b71d468acea62ce7b0

snyk-io Bot commented Jun 5, 2025 •

edited by sourcery-ai Bot

Loading

Uh oh!

codesandbox Bot commented Jun 5, 2025

Uh oh!

sourcery-ai Bot commented Jun 5, 2025 •

edited

Loading

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

graphite-app Bot Jun 5, 2025

Uh oh!

socket-security Bot commented Jun 5, 2025

Uh oh!

socket-security Bot commented Jun 5, 2025

Uh oh!

snyk-io Bot commented Jun 5, 2025

Uh oh!

github-actions Bot commented Jun 12, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

snyk-io Bot commented Jun 5, 2025 • edited by sourcery-ai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

Note for zero-installs users

Vulnerabilities that will be fixed with an upgrade:

Summary by Sourcery

Uh oh!

codesandbox Bot commented Jun 5, 2025

Review or Edit in CodeSandbox

Uh oh!

sourcery-ai Bot commented Jun 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

graphite-app Bot Jun 5, 2025

Choose a reason for hiding this comment

Uh oh!

socket-security Bot commented Jun 5, 2025

Uh oh!

socket-security Bot commented Jun 5, 2025

Uh oh!

snyk-io Bot commented Jun 5, 2025

⛔ Snyk checks have failed. 1 issues have been found so far.

Uh oh!

github-actions Bot commented Jun 12, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

snyk-io Bot commented Jun 5, 2025 •

edited by sourcery-ai Bot

Loading

sourcery-ai Bot commented Jun 5, 2025 •

edited

Loading