[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/home/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-AJV-15274295	157
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	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)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR pins Backstage plugin dependencies to specific versions in the home plugin package configuration.

• Replaced workspace:^ protocol with fixed version 1.0.0 for @backstage/plugin-catalog-react
• Replaced workspace:^ protocol with fixed version 0.1.0 for @backstage/plugin-home-react
• Changes made in plugins/home/package.json dependencies section
• Indicates preparation for plugin publishing or resolution of version compatibility issues

[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, aims to enhance the security posture of the project by upgrading specific Backstage plugin dependencies. The updates target critical vulnerabilities, ensuring the application remains robust against known exploits related to regular expression processing and resource allocation. The primary impact is improved security without significant functional changes.

Highlights

• Vulnerability Fixes: This pull request addresses two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
• Dependency Updates: To mitigate the identified vulnerabilities, the @backstage/plugin-catalog-react dependency has been updated to version 1.0.0 and @backstage/plugin-home-react has been updated to version 0.1.0 in plugins/home/package.json.
• Yarn Zero-Installs Note: Users employing Yarn's zero-installs feature should be aware that this PR does not update the .yarn/cache/ directory, requiring a manual yarn command to refresh the cache.

Changelog

• plugins/home/package.json
  • Updated @backstage/plugin-catalog-react from workspace:^ to 1.0.0.
  • Updated @backstage/plugin-home-react from workspace:^ to 0.1.0.

Activity

• Snyk automatically created this pull request to fix 2 vulnerabilities in yarn dependencies.
• The PR description includes details on the vulnerabilities (ReDoS and Allocation of Resources Without Limits or Throttling) and their severity scores.
• A warning is noted regarding the failure to update yarn.lock, advising manual update before merging.
• Guidance is provided for users of Yarn's zero-installs feature, indicating a manual yarn run is needed to update the cache.
• Links to Snyk reports, documentation, and interactive lessons on the vulnerabilities are included in the PR description.

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 passed. No issues have been found so far.

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

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates dependency management for the home plugin by replacing workspace protocol references with fixed version numbers. Two Backstage plugin dependencies are now pinned to specific versions: @backstage/plugin-catalog-react at version 1.0.0 and @backstage/plugin-home-react at version 0.1.0. This transition from workspace-relative dependencies (workspace:^) to explicit version pinning suggests the plugin is being prepared for independent distribution or addressing specific version compatibility requirements in the build pipeline.

Changes

File(s)	Summary
plugins/home/package.json	Changed dependency version specifications from workspace protocol (workspace:^) to fixed versions: @backstage/plugin-catalog-react pinned to 1.0.0 and @backstage/plugin-home-react pinned to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Home as @backstage/plugin-home
    participant CatalogReact as @backstage/plugin-catalog-react v1.0.0
    participant HomeReact as @backstage/plugin-home-react v0.1.0
    
    Note over Dev,HomeReact: Dependency Version Pinning Change
    
    Dev->>PM: Install dependencies for plugin-home
    activate PM
    
    PM->>Home: Read package.json
    Note over PM,Home: Dependencies changed from<br/>workspace:^ to fixed versions
    
    PM->>CatalogReact: Resolve @backstage/plugin-catalog-react
    Note right of CatalogReact: Now pinned to v1.0.0<br/>(previously workspace:^)
    CatalogReact-->>PM: Return v1.0.0
    
    PM->>HomeReact: Resolve @backstage/plugin-home-react
    Note right of HomeReact: Now pinned to v0.1.0<br/>(previously workspace:^)
    HomeReact-->>PM: Return v0.1.0
    
    PM-->>Dev: Dependencies installed with fixed versions
    deactivate PM
    
    Note over Dev,HomeReact: Impact: More predictable builds,<br/>but loses automatic workspace updates

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.

[gemini-code-assist]

Code Review

The pull request updates two @backstage dependencies in plugins/home/package.json from workspace:^ to specific versions 1.0.0 and 0.1.0 respectively. This change is intended to fix two vulnerabilities identified by Snyk. The PR description also notes a warning about yarn.lock not being updated, which might require manual intervention.

[gemini-code-assist]

Changing workspace:^ to a fixed version 1.0.0 for @backstage/plugin-catalog-react might prevent future automatic updates from the workspace. While this fixes the immediate vulnerability, it could lead to dependency drift if other packages in the monorepo are updated and this one is not. Consider if this package should always be aligned with the workspace version or if a specific version is truly required for the fix.

Suggested change

	"@backstage/plugin-catalog-react": "1.0.0",
	"@backstage/plugin-catalog-react": "workspace:^",

[gemini-code-assist]

Similar to the previous comment, fixing @backstage/plugin-home-react to 0.1.0 instead of workspace:^ could introduce challenges in maintaining consistent dependency versions across the monorepo. If the intention is to always use the latest compatible version within the workspace, workspace:^ is generally preferred. If this specific version is critical for the vulnerability fix, ensure this is documented and understood for future maintenance.

Suggested change

	"@backstage/plugin-home-react": "0.1.0",
	"@backstage/plugin-home-react": "workspace:^",

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