[Snyk] Fix for 2 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/search-backend-module-catalog/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
	Always-Incorrect Control Flow Implementation SNYK-JS-HTTPPROXYMIDDLEWARE-9691387	601
	Improper Check for Unusual or Exceptional Conditions SNYK-JS-HTTPPROXYMIDDLEWARE-9691389	601

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Summary by Sourcery

Update dependencies to fix security vulnerabilities in the search backend catalog module

Bug Fixes:

• Fix two medium-severity security vulnerabilities in http-proxy-middleware package

Enhancements:

• Update Backstage package dependencies to specific versions

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades three packages in plugins/search-backend-module-catalog/package.json to address two vulnerabilities identified by Snyk. The packages @backstage/backend-tasks, @backstage/plugin-catalog-common, and @backstage/plugin-search-common were upgraded to versions 0.6.1, 0.1.0, and 0.3.1, respectively.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The pull request upgrades three packages to address two vulnerabilities.	Upgraded @backstage/backend-tasks from workspace:^ to 0.6.1. Upgraded @backstage/plugin-catalog-common from workspace:^ to 0.1.0. Upgraded @backstage/plugin-search-common from workspace:^ to 0.3.1.	plugins/search-backend-module-catalog/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!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[graphite-app]

This PR replaces workspace:^ references with pinned versions, which breaks the Backstage monorepo dependency structure. In Backstage monorepos, internal package dependencies should use workspace references to maintain consistency across the codebase.

Pinning to specific versions (particularly older ones like 0.1.0) will likely cause compatibility issues with other components. The vulnerabilities in http-proxy-middleware should be addressed at the root level package.json rather than by pinning individual package versions.

Consider reverting these changes to maintain the workspace:^ references, and instead update the vulnerable dependency at the root level where it's actually defined. This approach will preserve the monorepo integrity while still addressing the security concerns.

Suggested change

	"@backstage/backend-tasks": "0.6.1",
	"@backstage/catalog-client": "workspace:^",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/plugin-catalog-common": "workspace:^",
	"@backstage/plugin-catalog-common": "0.1.0",
	"@backstage/plugin-permission-common": "workspace:^",
	"@backstage/plugin-search-backend-node": "workspace:^",
	"@backstage/plugin-search-common": "workspace:^"
	"@backstage/plugin-search-common": "0.3.1"
	"@backstage/backend-tasks": "workspace:^",
	"@backstage/catalog-client": "workspace:^",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/plugin-catalog-common": "workspace:^",
	"@backstage/plugin-permission-common": "workspace:^",
	"@backstage/plugin-search-backend-node": "workspace:^",
	"@backstage/plugin-search-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!