[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/catalog-backend-module-github/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	210
	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 catalog-backend-module-github plugin from workspace protocol dependencies to explicit version numbers for all Backstage packages.

• Replaced workspace:^ references with pinned versions for 7 Backstage packages
• Updated @backstage/backend-common to 0.24.1
• Updated @backstage/backend-plugin-api to 1.6.1
• Updated @backstage/catalog-model to 0.1.1
• Updated @backstage/integration to 0.1.0
• Updated @backstage/plugin-catalog-backend to 2.0.0
• Updated @backstage/plugin-catalog-common to 0.1.0
• Updated @backstage/plugin-events-node to 0.4.0
• Bumped lodash from ^4.17.21 to ^4.17.23

[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 present in the project's Yarn dependencies. It achieves this by updating several core @backstage packages and the lodash library to newer, more secure versions, enhancing the overall security posture of the application.

Highlights

• Dependency Updates: Several @backstage dependencies, including @backstage/backend-common, @backstage/backend-plugin-api, @backstage/catalog-model, @backstage/integration, @backstage/plugin-catalog-backend, @backstage/plugin-catalog-common, and @backstage/plugin-events-node, have been updated from workspace:^ to specific, newer versions.
• Vulnerability Fixes: The lodash package has been upgraded from ^4.17.21 to ^4.17.23 to address identified security vulnerabilities, specifically Prototype Pollution.
• Security Remediation: This pull request collectively fixes 6 vulnerabilities, including issues related to Improper Handling of Unicode Encoding, Use of a Cryptographic Primitive with a Risky Implementation, UNIX Symbolic Link (Symlink) Following, Prototype Pollution (in lodash and lodashes), and Regular Expression Denial of Service (ReDoS).
• Manual yarn.lock Update Required: A warning is present indicating that the yarn.lock file was not automatically updated and requires manual intervention before merging, especially for projects utilizing 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 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.

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the catalog-backend-module-github plugin by replacing workspace protocol references with explicit version numbers for Backstage packages. The changes affect multiple core dependencies including backend-common (0.24.1), backend-plugin-api (1.6.1), catalog-model (0.1.1), integration (0.1.0), plugin-catalog-backend (2.0.0), plugin-catalog-common (0.1.0), and plugin-events-node (0.4.0). Additionally, the lodash dependency is upgraded from 4.17.21 to 4.17.23. This transition from workspace protocol to pinned versions indicates preparation for a release or establishing more explicit version control outside of a monorepo workspace context.

Changes

File(s)

Summary

plugins/catalog-backend-module-github/package.json

Converted Backstage package dependencies from workspace protocol references (workspace:^) to explicit version numbers: @backstage/backend-common (0.24.1), @backstage/backend-plugin-api (1.6.1), @backstage/catalog-model (0.1.1), @backstage/integration (0.1.0), @backstage/plugin-catalog-backend (2.0.0), @backstage/plugin-catalog-common (0.1.0), @backstage/plugin-events-node (0.4.0). Updated lodash from ^4.17.21 to ^4.17.23.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as catalog-backend-module-github
    participant Deps as Updated Dependencies
    
    Note over Dev,Deps: Dependency Version Update (No Logic Changes)
    
    Dev->>PKG: Update package.json
    activate PKG
    
    PKG->>Deps: Update @backstage/backend-common<br/>workspace:^ → 0.24.1
    PKG->>Deps: Update @backstage/backend-plugin-api<br/>workspace:^ → 1.6.1
    PKG->>Deps: Update @backstage/catalog-model<br/>workspace:^ → 0.1.1
    PKG->>Deps: Update @backstage/integration<br/>workspace:^ → 0.1.0
    PKG->>Deps: Update @backstage/plugin-catalog-backend<br/>workspace:^ → 2.0.0
    PKG->>Deps: Update @backstage/plugin-catalog-common<br/>workspace:^ → 0.1.0
    PKG->>Deps: Update @backstage/plugin-events-node<br/>workspace:^ → 0.4.0
    PKG->>Deps: Update lodash<br/>^4.17.21 → ^4.17.23
    
    Deps-->>PKG: Dependencies resolved
    deactivate PKG
    PKG-->>Dev: package.json updated
    
    Note over Dev,Deps: No behavioral changes - version alignment only

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

This pull request, automatically generated by Snyk, aims to fix 6 vulnerabilities by updating dependencies. However, the proposed changes have critical issues that need to be addressed before merging.

The dependency updates seem to have been generated without correctly understanding the monorepo's workspace: setup. This has resulted in:

1. Severe Downgrades: Several key @backstage packages are being downgraded to very old, incompatible versions (e.g., @backstage/catalog-model to 0.1.1). This will likely cause build failures and runtime errors.
2. Major Upgrades: Other packages are receiving major version bumps (e.g., @backstage/plugin-catalog-backend to 2.0.0), which could introduce breaking changes that require manual intervention.

Furthermore, as noted in the pull request description, the yarn.lock file has not been updated. This is a critical omission that will prevent the dependency changes from being applied correctly and can lead to inconsistent builds.

Due to these issues, I recommend rejecting the automated changes in this PR. The vulnerabilities should be addressed by manually updating the dependencies, ensuring version compatibility within the monorepo, and then generating and committing the updated yarn.lock file.