[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/scaffolder-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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	140
	Insecure Randomness SNYK-JS-FORMIDABLE-9788127	57

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Insecure Randomness

Summary by Sourcery

Upgrade dependencies in scaffolder-backend to resolve security vulnerabilities and ensure compatibility with newer package versions.

Bug Fixes:

• Upgrade dependencies to address Regular Expression Denial of Service (ReDoS) and Insecure Randomness vulnerabilities.

Enhancements:

• Update specific @backstage dependencies from workspace references to fixed versions for improved security and stability.

[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

This PR updates specific dependencies in plugins/scaffolder-backend/package.json to fixed versions in order to address two security vulnerabilities identified by Snyk. The changes replace several 'workspace:^' dependency references with explicit version numbers, which may introduce breaking changes and require a manual yarn.lock update.

File-Level Changes

Change	Details	Files
Updated several @backstage dependencies from 'workspace:^' to explicit versions to address vulnerabilities.	Set @backstage/backend-common to 0.24.1 Set @backstage/config to 0.1.1 Set @backstage/plugin-catalog-backend to 1.25.0 Set @backstage/plugin-scaffolder-common to 0.1.0 Set @backstage/plugin-scaffolder-node to 0.1.0	plugins/scaffolder-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.

[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!

[graphite-app]

This PR changes several dependencies from workspace references (workspace:^) to specific pinned versions while leaving others as workspace references. This inconsistent approach in a monorepo setup can create dependency resolution problems and version conflicts.

The warning in the PR description confirms that the yarn.lock update failed, which is a significant concern. In a monorepo, it's generally recommended to maintain a consistent versioning strategy across related packages.

Consider either:

1. Keeping all dependencies as workspace references to maintain internal consistency
2. Properly updating the yarn.lock file if pinning specific versions

Without a properly updated lockfile, these changes may cause build or runtime issues when dependencies expect different versions of shared libraries.

Suggested change

	"@backstage/backend-common": "0.24.1",
	"@backstage/backend-plugin-api": "workspace:^",
	"@backstage/backend-tasks": "workspace:^",
	"@backstage/catalog-client": "workspace:^",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/config": "0.1.1",
	"@backstage/errors": "workspace:^",
	"@backstage/integration": "workspace:^",
	"@backstage/plugin-auth-node": "workspace:^",
	"@backstage/plugin-catalog-backend": "workspace:^",
	"@backstage/plugin-catalog-backend": "1.25.0",
	"@backstage/plugin-catalog-common": "workspace:^",
	"@backstage/plugin-catalog-node": "workspace:^",
	"@backstage/plugin-permission-common": "workspace:^",
	"@backstage/plugin-permission-node": "workspace:^",
	"@backstage/plugin-scaffolder-common": "workspace:^",
	"@backstage/plugin-scaffolder-node": "workspace:^",
	"@backstage/plugin-scaffolder-common": "0.1.0",
	"@backstage/plugin-scaffolder-node": "0.1.0",
	"@backstage/backend-common": "workspace:^",
	"@backstage/backend-plugin-api": "workspace:^",
	"@backstage/backend-tasks": "workspace:^",
	"@backstage/catalog-client": "workspace:^",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/errors": "workspace:^",
	"@backstage/integration": "workspace:^",
	"@backstage/plugin-auth-node": "workspace:^",
	"@backstage/plugin-catalog-backend": "workspace:^",
	"@backstage/plugin-catalog-common": "workspace:^",
	"@backstage/plugin-catalog-node": "workspace:^",
	"@backstage/plugin-permission-common": "workspace:^",
	"@backstage/plugin-permission-node": "workspace:^",
	"@backstage/plugin-scaffolder-common": "workspace:^",
	"@backstage/plugin-scaffolder-node": "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!