Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 21, 2026

snyk-top-banner

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

Snyk changed the following file(s):

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

codesandbox bot commented Jan 21, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

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 project's security posture by resolving five critical vulnerabilities detected by Snyk. It achieves this by updating key @backstage dependencies within the plugins/catalog/package.json file. While the package versions are updated, a manual step is required to synchronize the yarn.lock file and cache, ensuring a complete and consistent fix.

Highlights

  • Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses 5 identified security vulnerabilities within the project's yarn dependencies. These include issues related to Unicode encoding, cryptographic primitive usage, Cross-site Scripting (XSS), and Open Redirects.
  • Dependency Updates: The PR updates the versions of @backstage/core-plugin-api and @backstage/plugin-search-react in the plugins/catalog/package.json file to resolve the reported vulnerabilities.
  • Manual yarn.lock Update Required: A warning indicates that the yarn.lock file was not automatically updated by Snyk. Users of Yarn's zero-installs feature, or anyone else, will need to manually run yarn to update the cache and yarn.lock after merging this PR.
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

snyk-io bot commented Jan 21, 2026

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.

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm atob under CC-BY-3.0

License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS)

From: ?npm/atob@2.1.2

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/atob@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm caniuse-lite under CC-BY-4.0

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/@storybook/addon-controls@6.5.16npm/@storybook/builder-webpack5@6.5.16npm/@storybook/manager-webpack5@6.5.16npm/@storybook/react@6.5.16npm/caniuse-lite@1.0.30001378

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001378. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@entelligence-ai-pr-reviews
Copy link

Walkthrough

Changes

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Catalog as Catalog Plugin
    participant CoreAPI as @backstage/core-plugin-api
    participant SearchReact as @backstage/plugin-search-react

    Note over Dev,SearchReact: Dependency Version Update Process

    Dev->>PM: Update package.json dependencies
    Note right of Dev: Change workspace:^ to 0.1.0<br/>for core-plugin-api and search-react

    PM->>PM: Resolve dependency versions
    
    alt Installing Dependencies
        PM->>CoreAPI: Install version 0.1.0
        CoreAPI-->>PM: Package installed
        PM->>SearchReact: Install version 0.1.0
        SearchReact-->>PM: Package installed
    else Dependencies Already Cached
        PM->>PM: Use cached versions
    end

    PM->>Catalog: Link dependencies to plugin
    
    Note over Catalog,SearchReact: Plugin now uses pinned versions<br/>instead of workspace references
    
    Catalog-->>Dev: Build ready with fixed versions
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

@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 aims to fix vulnerabilities, but the proposed changes involve downgrading @backstage/core-plugin-api and @backstage/plugin-search-react to a very old version (0.1.0). This is highly problematic as the plugins/catalog package currently depends on much newer versions (1.5.3 and 1.6.4-next.0 respectively), as indicated by its CHANGELOG.md and the actual package.json files of those dependencies. This downgrade will likely introduce significant compatibility issues, build failures, or even reintroduce older vulnerabilities. Additionally, the yarn.lock file was not updated, which is crucial for consistent dependency resolution.

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

Choose a reason for hiding this comment

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

critical

The dependency @backstage/core-plugin-api is being downgraded from workspace:^ (which resolves to a much newer version like 1.5.3) to 0.1.0. This is a significant downgrade and will likely cause severe compatibility issues and runtime errors, potentially reintroducing vulnerabilities instead of fixing them. Please ensure the dependency is upgraded to a secure and compatible version, not downgraded.

Suggested change
"@backstage/core-plugin-api": "0.1.0",
"@backstage/core-plugin-api": "^1.5.3",

"@backstage/plugin-scaffolder-common": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-search-react": "workspace:^",
"@backstage/plugin-search-react": "0.1.0",

Choose a reason for hiding this comment

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

critical

Similar to @backstage/core-plugin-api, the @backstage/plugin-search-react dependency is being downgraded from workspace:^ (which resolves to a much newer version like 1.6.4-next.0) to 0.1.0. This will almost certainly lead to breakage. Please update this dependency to a compatible and secure version.

Suggested change
"@backstage/plugin-search-react": "0.1.0",
"@backstage/plugin-search-react": "^1.6.4",

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.

3 participants