Skip to content

[Snyk] Fix for 6 vulnerabilities#10721

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-b965cf84eefeedca88ed3aec3e643f31
Closed

[Snyk] Fix for 6 vulnerabilities#10721
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-b965cf84eefeedca88ed3aec3e643f31

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Jan 24, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/catalog-node/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
medium severity Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  208  
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  146  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  113  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  88  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  88  
medium severity 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

Updated dependency version specifications in catalog-node plugin from workspace references to explicit npm package versions.

  • Changed @backstage/backend-plugin-api from 'workspace:^' to '1.6.1'
  • Changed @backstage/catalog-model from 'workspace:^' to '0.1.1'
  • Changed @backstage/errors from 'workspace:^' to '0.1.1'
  • Changed @backstage/plugin-catalog-common from 'workspace:^' to '0.1.0'
  • Indicates preparation for package publication or transition away from monorepo workspace dependencies

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 24, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! 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 aims to enhance the security posture of the project by resolving six identified vulnerabilities in its Yarn dependencies. It achieves this by updating specific @backstage package versions within the plugins/catalog-node/package.json file, moving from workspace references to explicit version numbers. This change is crucial for mitigating potential security risks and maintaining a robust dependency chain.

Highlights

  • Security Vulnerability Resolution: This pull request, automatically generated by Snyk, addresses 6 identified security vulnerabilities within the project's yarn dependencies. These include issues such as Improper Handling of Unicode Encoding (SNYK-JS-TAR-15038581), Use of a Cryptographic Primitive with a Risky Implementation (SNYK-JS-ELLIPTIC-14908844), UNIX Symbolic Link Following (SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291), Prototype Pollution (SNYK-JS-LODASH-15053838, SNYK-JS-LODASHES-15053836), and Regular Expression Denial of Service (ReDoS) (SNYK-JS-DIFF-14917201).
  • Dependency Version Updates: The plugins/catalog-node/package.json file has been updated to pin specific versions for several @backstage dependencies. Specifically, @backstage/backend-plugin-api is now 1.6.1, @backstage/catalog-model is 0.1.1, @backstage/errors is 0.1.1, and @backstage/plugin-catalog-common is 0.1.0, moving from workspace:^ references to explicit version numbers.
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
Copy link
Copy Markdown

snyk-io Bot commented Jan 24, 2026

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
Copy link
Copy Markdown

Walkthrough

This PR updates the dependency management approach for the catalog-node plugin by replacing workspace protocol references with explicit version numbers. Four Backstage packages are affected: backend-plugin-api (1.6.1), catalog-model (0.1.1), errors (0.1.1), and plugin-catalog-common (0.1.0). This change transitions from monorepo workspace dependencies to published npm package versions, which is typically done when preparing a package for independent publication or distribution outside the monorepo environment.

Changes

File(s) Summary
plugins/catalog-node/package.json Replaced workspace protocol references (workspace:^) with explicit version numbers for four dependencies: @backstage/backend-plugin-api (1.6.1), @backstage/catalog-model (0.1.1), @backstage/errors (0.1.1), and @backstage/plugin-catalog-common (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    participant CatalogNode as catalog-node Plugin

    Note over Dev,CatalogNode: Dependency Resolution Change (Build Time)
    
    Dev->>PM: Update package.json dependencies
    Note right of Dev: Pin workspace deps to versions:<br/>backend-plugin-api: 1.6.1<br/>catalog-model: 0.1.1<br/>errors: 0.1.1<br/>catalog-common: 0.1.0
    
    PM->>Registry: Resolve @backstage/backend-plugin-api@1.6.1
    Registry-->>PM: Return package
    
    PM->>Registry: Resolve @backstage/catalog-model@0.1.1
    Registry-->>PM: Return package
    
    PM->>Registry: Resolve @backstage/errors@0.1.1
    Registry-->>PM: Return package
    
    PM->>Registry: Resolve @backstage/plugin-catalog-common@0.1.0
    Registry-->>PM: Return package
    
    PM->>CatalogNode: Install pinned dependencies
    Note over CatalogNode: Dependencies now use<br/>fixed versions instead of<br/>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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, attempts to fix security vulnerabilities by pinning several @backstage dependencies to specific versions. However, this approach has critical flaws and should not be merged as-is. The changes break the monorepo's workspace linking by replacing workspace:^ with fixed versions. More critically, this PR downgrades several key packages to much older major versions (e.g., @backstage/catalog-model from 1.4.1 to 0.1.1), which will almost certainly introduce breaking changes and cause build failures. Additionally, as noted in the PR description, the yarn.lock file has not been updated, which would also need to be addressed. A safer approach to fix these vulnerabilities would be to use Yarn's resolutions feature in the root package.json to target and upgrade only the vulnerable transitive dependencies, without altering the primary dependency structure.

Comment on lines +39 to +43
"@backstage/backend-plugin-api": "1.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/catalog-model": "0.1.1",
"@backstage/errors": "0.1.1",
"@backstage/plugin-catalog-common": "0.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

These dependency changes are highly problematic and will likely break the project.

  1. Breaking Workspace Linking: By removing workspace:^, you are decoupling this package from the versions being developed within this monorepo. This defeats a primary purpose of using a monorepo with workspaces and can lead to using stale code and hard-to-debug integration issues.

  2. Major Version Downgrades: This change downgrades several packages to significantly older, incompatible versions:

    • @backstage/catalog-model: from workspace version 1.4.1 to 0.1.1
    • @backstage/errors: from workspace version 1.2.1 to 0.1.1
    • @backstage/plugin-catalog-common: from workspace version 1.0.15 to 0.1.0

    Such drastic downgrades across major versions are guaranteed to cause API incompatibilities and break the build.

It is recommended to revert these changes. To fix the underlying security vulnerabilities, consider using Yarn's resolutions field in the root package.json to force specific versions of the vulnerable transitive dependencies.

Suggested change
"@backstage/backend-plugin-api": "1.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/catalog-model": "0.1.1",
"@backstage/errors": "0.1.1",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",

@github-actions
Copy link
Copy Markdown

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!

@github-actions github-actions Bot added the stale label Jan 31, 2026
@github-actions github-actions Bot closed this Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants