[Snyk] Fix for 2 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	590
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	550

---

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)

---

EntelligenceAI PR Summary

Updated dependency version specifications in catalog-node plugin to prepare for npm registry publication.

• 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'
• Transitions from monorepo workspace protocol to explicit versioning for external distribution

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[snyk-io]

⛔ 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]

Walkthrough

This PR updates the dependency management configuration in the catalog-node plugin's package.json file. The changes replace workspace protocol references (workspace:^) with explicit version numbers for four Backstage packages: backend-plugin-api (1.6.1), catalog-model (0.1.1), errors (0.1.1), and plugin-catalog-common (0.1.0). This modification is a standard preparation step for publishing the package to the npm registry, as workspace protocols are used for local monorepo development while external distribution requires explicit version specifications.

Changes

File(s)	Summary
plugins/catalog-node/package.json	Replaced workspace protocol references with explicit version numbers for four Backstage 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,Registry: Dependency Resolution Change
    
    Dev->>PM: Update package.json dependencies
    Note over PM: Changed from workspace:^ to fixed versions:<br/>- backend-plugin-api: 1.6.1<br/>- catalog-model: 0.1.1<br/>- errors: 0.1.1<br/>- plugin-catalog-common: 0.1.0
    
    PM->>Registry: Resolve @backstage/backend-plugin-api@1.6.1
    Registry-->>PM: Return specific version
    
    PM->>Registry: Resolve @backstage/catalog-model@0.1.1
    Registry-->>PM: Return specific version
    
    PM->>Registry: Resolve @backstage/errors@0.1.1
    Registry-->>PM: Return specific version
    
    PM->>Registry: Resolve @backstage/plugin-catalog-common@0.1.0
    Registry-->>PM: Return specific version
    
    PM->>CatalogNode: Install pinned dependencies
    
    Note over CatalogNode: Dependencies now locked to<br/>specific 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.

[github-actions]

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!