[Snyk] Fix for 6 vulnerabilities

[q1blue]

Snyk has created this PR to fix 6 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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	208
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	113
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Prototype Pollution SNYK-JS-LODASHES-15053836	88
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	62

---

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)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

This PR transitions the azure-sites plugin from workspace protocol dependencies to explicit version pinning for three Backstage packages.

• Changed @backstage/core-components from workspace protocol to fixed version 0.1.0
• Changed @backstage/plugin-azure-sites-common from workspace protocol to fixed version 0.1.0
• Changed @backstage/plugin-catalog-react from workspace protocol to fixed version 0.0.1
• Enables independent package publishing or stricter version control

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, addresses six security vulnerabilities by updating specific @backstage dependencies within the plugins/azure-sites package. The primary goal is to enhance the project's security by upgrading vulnerable components to their patched versions.

Highlights

• Vulnerability Fixes: This pull request addresses and fixes 6 identified security vulnerabilities across various dependencies, including one high-severity and five medium-severity issues.
• Dependency Updates: The plugins/azure-sites/package.json file has been updated to specify exact versions for @backstage/core-components, @backstage/plugin-azure-sites-common, and @backstage/plugin-catalog-react, moving away from workspace:^.
• Yarn Lock Warning: A warning is present indicating that the yarn.lock file failed to update and requires manual intervention before merging to ensure dependency consistency.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[snyk-io]

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

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	0	1	0	1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix 6 vulnerabilities by updating dependencies in plugins/azure-sites/package.json. However, the proposed changes pin several @backstage packages to very old versions instead of using the workspace:^ protocol appropriate for this monorepo. This will likely break the application due to version mismatches and API incompatibilities. Furthermore, the PR description notes that yarn.lock could not be updated, confirming that these changes introduce dependency resolution issues. I have recommended rejecting these changes and instead using Yarn's resolutions feature to address the underlying transitive dependency vulnerabilities without breaking the project's structure.

[gemini-code-assist]

These version changes from workspace:^ to fixed, very old versions are likely to break the application. In a monorepo setup like this, packages are expected to use the versions from the current workspace. Pinning to old versions can lead to API incompatibilities and other issues.

For example:

• @backstage/core-components is pinned to 0.1.0, but the workspace version is 0.13.4-next.0.
• @backstage/plugin-catalog-react is pinned to 0.0.1, but the workspace version is 1.8.1-next.0.

Instead of pinning these direct dependencies, consider using Yarn's resolutions feature in the root package.json to force newer, non-vulnerable versions of the transitive dependencies that Snyk has flagged. This will fix the security issues without breaking the internal dependencies of the monorepo.

The PR description also notes that yarn.lock failed to update, which is a strong indication that these changes introduce dependency conflicts. It's best to revert these changes and address the vulnerabilities via resolutions.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/plugin-azure-sites-common": "workspace:^",
    "@backstage/plugin-catalog-react": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the azure-sites plugin by transitioning from workspace protocol references to explicit version pinning. Three Backstage packages are affected: @backstage/core-components is pinned to version 0.1.0, @backstage/plugin-azure-sites-common is pinned to version 0.1.0, and @backstage/plugin-catalog-react is pinned to version 0.0.1. This change moves away from monorepo workspace dependencies to fixed version specifications, which typically indicates preparation for independent package publication or the establishment of stricter version control policies across the codebase.

Changes

File(s)	Summary
plugins/azure-sites/package.json	Updated three Backstage package dependencies from workspace protocol to fixed versions: @backstage/core-components to 0.1.0, @backstage/plugin-azure-sites-common to 0.1.0, and @backstage/plugin-catalog-react to 0.0.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    
    Note over Dev,Registry: Dependency Version Update Process
    
    Dev->>PM: Update package.json dependencies
    Note right of Dev: Change workspace:^ to<br/>specific versions
    
    PM->>Registry: Resolve @backstage/core-components@0.1.0
    Registry-->>PM: Return package metadata
    
    PM->>Registry: Resolve @backstage/plugin-azure-sites-common@0.1.0
    Registry-->>PM: Return package metadata
    
    PM->>Registry: Resolve @backstage/plugin-catalog-react@0.0.1
    Registry-->>PM: Return package metadata
    
    PM->>PM: Update lock file
    PM-->>Dev: Dependencies resolved
    
    Note over Dev,Registry: No runtime behavior changes<br/>Only dependency version pinning

Loading

▶️ ⚡ AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf

Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

• ⚠️ Potential Issue - May require further investigation.
• 🔒 Security Vulnerability - Fix to ensure system safety.
• 💻 Code Improvement - Suggestions to enhance code quality.
• 🔨 Refactor Suggestion - Recommendations for restructuring code.
• ℹ️ Others - General comments and information.

Interact with the Bot:

• Send a message or request using the format:
  @entelligenceai + *your message*

Example: @entelligenceai Can you suggest improvements for this code?

• Help the Bot learn by providing feedback on its responses.
  @entelligenceai + *feedback*

Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

1. config - shows the current config
2. retrigger_review - retriggers the review

More commands to be added soon.