Skip to content

[Snyk] Security upgrade @backstage/plugin-search-react from 0.0.0-use.local to 0.1.0#11873

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-f8ee97f0fb6d0af6fea7d3c1a69911be
Open

[Snyk] Security upgrade @backstage/plugin-search-react from 0.0.0-use.local to 0.1.0#11873
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-f8ee97f0fb6d0af6fea7d3c1a69911be

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Feb 7, 2026

snyk-top-banner

Snyk has created this PR to fix 2 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
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  380  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  380  

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:

🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR pins the @backstage/plugin-search-react dependency to a specific version in the catalog plugin.

  • Updated dependency version from workspace:^ to 0.1.0 in plugins/catalog/package.json
  • Transitions from local workspace reference to published package version
  • Ensures consistent dependency resolution across environments

@codesandbox
Copy link

codesandbox bot commented Feb 7, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Author

snyk-io bot commented Feb 7, 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

Walkthrough

This pull request modifies the dependency management for the catalog plugin by changing how it references the search-react plugin. The change transitions from using a workspace protocol reference (which points to the local monorepo version) to a fixed version number (0.1.0). This type of modification typically occurs when preparing for a release, resolving version compatibility issues, or ensuring consistent dependency versions across environments. The pinned version provides more predictable behavior and may be necessary for proper package resolution in production deployments.

Changes

File(s) Summary
plugins/catalog/package.json Changed @backstage/plugin-search-react dependency from workspace protocol reference (workspace:^) to fixed version 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Build as Build System
    participant Catalog as @backstage/plugin-catalog
    participant SearchReact as @backstage/plugin-search-react

    Note over Dev,SearchReact: Dependency Version Change (workspace:^ → 0.1.0)
    
    Dev->>Build: Run package install
    Build->>Catalog: Resolve dependencies
    
    alt Before Change
        Catalog->>Build: Request workspace:^ version
        Build->>SearchReact: Use local workspace version
    else After Change
        Catalog->>Build: Request version 0.1.0
        Build->>SearchReact: Use published package v0.1.0
    end
    
    SearchReact-->>Catalog: Dependency resolved
    Build-->>Dev: Installation complete
    
    Note over Catalog,SearchReact: Runtime behavior unchanged<br/>Only dependency resolution differs
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.

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.

0 participants