[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/catalog-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
	Improper Link Resolution Before File Access ('Link Following') SNYK-JS-TARFS-10293725	721

---

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:

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

Summary by Sourcery

Bug Fixes:

• Upgrade @backstage/backend-common, plugin-scaffolder-common, plugin-search-backend-module-catalog, and plugin-search-common to patched versions to address the Improper Link Resolution vulnerability.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's Guide

This PR fixes a high-severity tar-fs vulnerability by replacing workspace dependency ranges with specific, patched versions in the catalog-backend package.

Flow Diagram: Dependency Updates by Snyk in this PR

graph TD
    A["Snyk identifies vulnerability (SNYK-JS-TARFS-10293725)<br>affecting dependencies in<br>'plugins/catalog-backend/package.json'"] --> B["This Pull Request proposes the following changes to 'package.json':"];
    B --> U1["Update '@backstage/backend-common'<br>from 'workspace:^' to '0.24.1'"];
    B --> U2["Update '@backstage/plugin-scaffolder-common'<br>from 'workspace:^' to '0.1.0'"];
    B --> U3["Update '@backstage/plugin-search-backend-module-catalog'<br>from 'workspace:^' to '0.2.0'"];
    B --> U4["Update '@backstage/plugin-search-common'<br>from 'workspace:^' to '0.3.1'"];
    Outcome["Outcome: Vulnerability addressed by<br>using fixed dependency versions."]
    U1 --> Outcome;
    U2 --> Outcome;
    U3 --> Outcome;
    U4 --> Outcome;

Loading

File-Level Changes

Change	Details	Files
Pinned several @backstage dependencies to explicit patched versions	Replaced workspace:^ range for backend-common with 0.24.1 Updated plugin-scaffolder-common to 0.1.0 Updated plugin-search-backend-module-catalog to 0.2.0 Updated plugin-search-common to 0.3.1	plugins/catalog-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.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[graphite-app]

Replacing workspace:^ with a fixed version 0.24.1 breaks the monorepo dependency management pattern. This change will likely cause version conflicts when other packages in the workspace expect to use the local version of @backstage/backend-common.

In a monorepo setup, workspace:^ ensures all packages use consistent versions of shared dependencies. Consider maintaining this pattern to avoid potential integration issues during development and testing.

Suggested change

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

Spotted by Diamond

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

[github-actions]

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!