[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/azure-sites/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	738

---

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)

Summary by Sourcery

Update package dependencies to resolve a security vulnerability in the Azure Sites plugin

Bug Fixes:

• Fix a Regular Expression Denial of Service (ReDoS) vulnerability in @babel/runtime

Enhancements:

• Update workspace dependencies to specific package 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

This pull request, automatically generated by Snyk, addresses a Regular Expression Denial of Service (ReDoS) vulnerability. This is achieved by updating the versions of four @backstage dependencies specified in the plugins/azure-sites/package.json file. Please note, the yarn.lock file was not updated and requires manual regeneration before merging.

Sequence Diagram for Snyk Vulnerability Fix Process

sequenceDiagram
    actor Snyk
    participant Repo as "Project Repository"
    actor Developer

    Snyk->>Repo: Scans for vulnerabilities
    Snyk->>Repo: Detects ReDoS vulnerability in 'plugins/azure-sites/package.json'
    Snyk->>Repo: Creates PR with dependency version updates
    Repo->>Developer: Notifies about new PR
    Developer->>Repo: Reviews PR (sees 'package.json' changes)
    note right of Developer: PR description warns: 'yarn.lock' needs manual update.
    Developer->>Developer: Runs 'yarn' (or equivalent) locally to update 'yarn.lock'
    Developer->>Repo: Commits updated 'yarn.lock' to the PR branch
    Developer->>Repo: Merges PR

Loading

File-Level Changes

Change	Details	Files
Upgraded versions of multiple @backstage dependencies to mitigate a reported vulnerability.	Updated @backstage/core-components dependency version. Updated @backstage/plugin-azure-sites-common dependency version. Updated @backstage/plugin-catalog-react dependency version. Updated @backstage/theme dependency version.	plugins/azure-sites/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]

This PR replaces workspace references with fixed versions, which disrupts the project's workspace dependency management system. This approach:

1. Breaks the internal dependency resolution that workspace:^ provides
2. May introduce version conflicts with other packages in the workspace
3. Could create build issues as confirmed by the failed yarn.lock update

A more sustainable approach would be to maintain the workspace references while addressing the vulnerability in @babel/runtime through:

• Updating the affected package within the workspace
• Adding resolutions in the root package.json to force a specific version of @babel/runtime
• Using yarn's selective dependency resolution features

This would fix the vulnerability while preserving the workspace integrity and dependency management system.

Suggested change

	"@backstage/core-components": "0.1.0",
	"@backstage/core-plugin-api": "workspace:^",
	"@backstage/plugin-azure-sites-common": "workspace:^",
	"@backstage/plugin-catalog-react": "workspace:^",
	"@backstage/theme": "workspace:^",
	"@backstage/plugin-azure-sites-common": "0.1.0",
	"@backstage/plugin-catalog-react": "0.0.1",
	"@backstage/theme": "0.1.1",
	+ "@backstage/core-components": "workspace:^",
	"@backstage/core-plugin-api": "workspace:^",
	+ "@backstage/plugin-azure-sites-common": "workspace:^",
	+ "@backstage/plugin-catalog-react": "workspace:^",
	+ "@backstage/theme": "workspace:^",

Spotted by Diamond

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

[snyk-io]

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

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!