[Snyk] Security upgrade @backstage/plugin-catalog from 0.0.0-use.local to 0.1.1

[q1blue]

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

Snyk changed the following file(s):

• plugins/catalog-customized/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
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	Cross-site Scripting (XSS) SNYK-JS-REMIXRUNROUTER-14908530	134
	Open Redirect SNYK-JS-REACTROUTER-14908286	114
	Open Redirect SNYK-JS-REMIXRUNROUTER-14908287	114

---

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:

🦉 Open Redirect
🦉 Cross-site Scripting (XSS)

[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 project's security posture by upgrading a critical dependency. The upgrade targets specific vulnerabilities within the @backstage/plugin-catalog package, ensuring a more secure application environment by resolving known security flaws.

Highlights

• Dependency Upgrade: Upgraded the @backstage/plugin-catalog dependency from 0.0.0-use.local to 0.1.1 in plugins/catalog-customized/package.json.
• Security Vulnerability Fixes: This upgrade addresses 4 identified security vulnerabilities, including a medium severity 'Use of a Cryptographic Primitive with a Risky Implementation' and three high severity issues: 'Cross-site Scripting (XSS)' and two 'Open Redirect' vulnerabilities.
• Manual yarn.lock Update Required: The yarn.lock file was not automatically updated by Snyk and requires manual intervention before merging to ensure dependency consistency, especially for projects not using Yarn's zero-installs feature.

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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix security vulnerabilities by changing the version of @backstage/plugin-catalog. However, the proposed change from workspace:^ to a fixed version 0.1.1 is a major downgrade from the current workspace version (1.12.1-next.0) and will likely break the application. I've left a comment suggesting to revert this change. The correct approach would be to update the dependencies of the @backstage/plugin-catalog package within your monorepo. Additionally, as noted in the PR description, the yarn.lock file has not been updated, which is required after any dependency change.

[gemini-code-assist]

This change replaces the workspace dependency on @backstage/plugin-catalog with a pinned, very old version (0.1.1). The local version of @backstage/plugin-catalog in this monorepo is 1.12.1-next.0 (as seen in plugins/catalog/package.json). This is a significant downgrade and will likely cause build failures or runtime errors due to API incompatibilities.

Using workspace:^ ensures you are using the code from your local monorepo, which is the intended setup. Pinning to an external version, especially a very old one, breaks this. The correct way to fix the underlying security vulnerabilities is likely to update the dependencies within the local @backstage/plugin-catalog package itself.

Suggested change

	"@backstage/plugin-catalog": "0.1.1",
	"@backstage/plugin-catalog": "workspace:^",

[entelligence-ai-pr-reviews]

Walkthrough

Changes

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace
    participant Reg as NPM Registry
    participant Plugin as catalog-customized

    Dev->>PM: Install dependencies
    PM->>Plugin: Read package.json
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/plugin-catalog
        WS-->>PM: Return local workspace version
        PM->>Plugin: Link workspace dependency
    else After Change (0.1.1)
        PM->>Reg: Fetch @backstage/[email protected]
        Reg-->>PM: Return version 0.1.1
        PM->>Plugin: Install specific version
    end
    
    PM-->>Dev: Dependencies installed
    Note over Plugin: Plugin now uses pinned version<br/>instead of workspace reference

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.