Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 10, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/catalog-common/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
high severity Cross-site Scripting (XSS)
SNYK-JS-REMIXRUNROUTER-14908530
  171  
high severity Open Redirect
SNYK-JS-REACTROUTER-14908286
  144  
high severity Open Redirect
SNYK-JS-REMIXRUNROUTER-14908287
  144  

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 10, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link

snyk-io bot commented Jan 10, 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.

@entelligence-ai-pr-reviews
Copy link

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PkgJson as catalog-common/package.json
    participant PM as Package Manager
    participant SearchCommon as plugin-search-common

    Note over Dev,SearchCommon: Dependency Version Pinning Change

    Dev->>PkgJson: Update dependency version
    Note right of PkgJson: Change from workspace:^<br/>to version 0.3.1
    
    Dev->>PM: Install dependencies
    PM->>SearchCommon: Resolve plugin-search-common
    
    alt Version 0.3.1 available
        SearchCommon-->>PM: Return v0.3.1 package
        PM-->>PkgJson: Install pinned version
    else Version not found
        SearchCommon-->>PM: Error: Version not found
        PM-->>Dev: Installation failed
    end
    
    Note over PkgJson,SearchCommon: catalog-common now uses<br/>fixed version instead of<br/>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.

@augmentcode
Copy link

augmentcode bot commented Jan 10, 2026

🤖 Augment PR Summary

Summary: Pins @backstage/plugin-search-common in plugins/catalog-common from a workspace reference to version 0.3.1 (Snyk-driven).
Intent: Reduce Snyk-reported high-severity transitive vulnerabilities (XSS/open-redirect) by upgrading dependency resolution.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

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

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

"@backstage/catalog-model": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-search-common": "workspace:^"
"@backstage/plugin-search-common": "0.3.1"
Copy link

Choose a reason for hiding this comment

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

@backstage/plugin-search-common is also a local workspace package in this repo (plugins/search-common, currently v1.2.5); pinning 0.3.1 will force Yarn to fetch an older external copy instead of using the workspace package.
This can introduce duplicate/mismatched Backstage packages and break builds/runtime expectations in the monorepo.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

"@backstage/catalog-model": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-search-common": "workspace:^"
"@backstage/plugin-search-common": "0.3.1"
Copy link

Choose a reason for hiding this comment

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

Snyk notes the lockfile update failed; since yarn.lock isn’t updated in this PR, CI may still resolve the previous dependency graph (or fail due to an out-of-sync lockfile).
Before merging, make sure the lockfile reflects the intended resolution for this dependency change (especially if using zero-installs).

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

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