[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/home-react/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 home-react plugin from workspace-based dependencies to explicit version pinning for core Backstage packages.

• Changed @backstage/core-components dependency from workspace:^ to 0.1.0
• Changed @backstage/core-plugin-api dependency from workspace:^ to 0.1.0
• Shifts from monorepo workspace dependency resolution to explicit version references
• Likely prepares the plugin for independent package distribution

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

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, initiated by Snyk, focuses on improving the project's security posture by resolving several identified vulnerabilities in its yarn dependencies. The core change involves updating specific @backstage package versions to their stable 0.1.0 release. While addressing critical security concerns, it also highlights the need for manual yarn.lock updates and considerations for zero-install environments to ensure a smooth integration.

Highlights

• Security Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses 6 identified vulnerabilities within the project's yarn dependencies.
• Dependency Version Updates: The @backstage/core-components and @backstage/core-plugin-api dependencies in plugins/home-react/package.json have been explicitly set to version 0.1.0 from their previous workspace:^ references.
• Manual yarn.lock Update Required: A warning indicates that the yarn.lock file was not automatically updated and requires manual intervention before merging.
• Zero-Install Consideration: Users leveraging Yarn's zero-install feature are advised to run yarn locally to update their .yarn/cache/ directory after pulling these changes.

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. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix several vulnerabilities by updating dependencies. However, the proposed changes in plugins/home-react/package.json are incorrect. It pins @backstage/core-components and @backstage/core-plugin-api to version 0.1.0, which is a major downgrade from the versions used in the workspace. This will likely lead to build failures and runtime errors. The changes should be reverted, and the vulnerabilities should be addressed by updating the workspace packages themselves if necessary.

[gemini-code-assist]

These dependency versions are being pinned to 0.1.0, which is a significant downgrade from the versions available in the workspace (@backstage/core-components is at 0.13.4-next.0 and @backstage/core-plugin-api is at 1.5.3). This will almost certainly cause breaking changes and build failures, as the rest of the code in this package expects much newer APIs.

While this change was likely automated by Snyk to fix vulnerabilities, the chosen versions are incorrect. Instead of pinning to these old versions, the workspace:^ protocol should be kept. If there are vulnerabilities, the packages in the workspace themselves should be updated. Please revert this change.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the home-react plugin by replacing workspace protocol references with explicit version pinning. The change affects two core Backstage dependencies, transitioning from workspace:^ (which resolves to local monorepo packages during development) to fixed version 0.1.0. This modification suggests the plugin is being prepared for independent distribution or moving away from monorepo-style dependency resolution. The change impacts how package managers resolve these dependencies and may affect the plugin's compatibility with different Backstage versions.

Changes

File(s)	Summary
plugins/home-react/package.json	Updated dependency version constraints for @backstage/core-components and @backstage/core-plugin-api from workspace protocol (workspace:^) to fixed version 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as package.json
    participant NPM as Package Manager
    participant WS as Workspace Packages
    participant REG as NPM Registry

    Note over Dev,REG: Dependency Resolution Change

    Dev->>PKG: Update dependencies
    Note over PKG: @backstage/core-components<br/>workspace:^ → 0.1.0<br/>@backstage/core-plugin-api<br/>workspace:^ → 0.1.0

    rect rgb(240, 240, 240)
        Note over NPM,REG: Before Change (workspace:^)
        Dev->>NPM: npm install
        NPM->>WS: Resolve workspace dependencies
        WS-->>NPM: Return local packages
        NPM-->>Dev: Install from workspace
    end

    rect rgb(220, 240, 220)
        Note over NPM,REG: After Change (0.1.0)
        Dev->>NPM: npm install
        NPM->>REG: Fetch @backstage/core-components@0.1.0
        REG-->>NPM: Return published package
        NPM->>REG: Fetch @backstage/core-plugin-api@0.1.0
        REG-->>NPM: Return published package
        NPM-->>Dev: Install from registry
    end

    Note over Dev,REG: Plugin now uses fixed versions<br/>instead of workspace references

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.