Skip to content

[Snyk] Fix for 1 vulnerabilities#12075

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-7067fbb8f640a3c3d34494bff804f25e
Closed

[Snyk] Fix for 1 vulnerabilities#12075
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-7067fbb8f640a3c3d34494bff804f25e

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to fix 1 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 Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  590  

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:

🦉 Allocation of Resources Without Limits or Throttling


EntelligenceAI PR Summary

This PR pins Backstage dependencies to explicit versions in the catalog-node plugin package, replacing workspace protocol references.

  • Updated @backstage/backend-plugin-api from workspace:^ to version 0.6.19
  • Updated @backstage/catalog-model from workspace:^ to version 0.1.1
  • Updated @backstage/errors from workspace:^ to version 0.1.1
  • Updated @backstage/plugin-catalog-common from workspace:^ to version 0.1.0
  • Changes made in plugins/catalog-node/package.json

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Feb 13, 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 strategy for the catalog-node plugin by replacing workspace protocol references with explicit version numbers. Four Backstage packages are affected: backend-plugin-api (0.6.19), catalog-model (0.1.1), errors (0.1.1), and plugin-catalog-common (0.1.0). This change transitions the package from using workspace-relative dependency resolution to pinned versions, which is a standard practice when preparing a package for publication or when moving away from monorepo development patterns to ensure consistent dependency resolution across different environments.

Changes

File(s) Summary
plugins/catalog-node/package.json Replaced workspace protocol (workspace:^) with explicit version numbers for four dependencies: @backstage/backend-plugin-api (0.6.19), @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 Plugin as catalog-node Plugin

    Note over Dev,Plugin: Dependency Version Update Process

    Dev->>Plugin: Update package.json<br/>(workspace:^ → fixed versions)
    
    Note over Plugin: Dependencies changed:<br/>- backend-plugin-api: 0.6.19<br/>- catalog-model: 0.1.1<br/>- errors: 0.1.1<br/>- plugin-catalog-common: 0.1.0
    
    Dev->>PM: Run install command
    PM->>Registry: Resolve fixed versions
    Registry-->>PM: Return package metadata
    PM->>Registry: Download packages<br/>(0.6.19, 0.1.1, 0.1.1, 0.1.0)
    Registry-->>PM: Package tarballs
    PM->>Plugin: Install dependencies
    
    Note over Plugin: Dependencies locked to<br/>specific versions instead<br/>of 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.

@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 Feb 20, 2026
@github-actions github-actions Bot closed this Mar 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.

0 participants