[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/catalog-backend-module-openapi/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
	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 transitions the catalog-backend-module-openapi plugin from workspace protocol dependencies to pinned external package versions.

• Updated @backstage/backend-common from workspace reference to version 0.24.1
• Updated @backstage/config from workspace reference to version 0.1.1
• Updated @backstage/plugin-catalog-backend from workspace reference to version 2.0.0
• Updated @backstage/plugin-catalog-common from workspace reference to version 0.1.0
• Changes made in plugins/catalog-backend-module-openapi/package.json

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[snyk-io]

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

Walkthrough

This PR updates the dependency management strategy for the catalog-backend-module-openapi plugin by replacing workspace protocol references with explicit version numbers for four Backstage packages. The changes pin @backstage/backend-common to 0.24.1, @backstage/config to 0.1.1, @backstage/plugin-catalog-backend to 2.0.0, and @backstage/plugin-catalog-common to 0.1.0. This transition from monorepo workspace dependencies to fixed external package versions suggests preparation for independent module distribution or a move toward stricter version control and stability guarantees.

Changes

File(s)	Summary
plugins/catalog-backend-module-openapi/package.json	Replaced workspace protocol dependency references with explicit version numbers for four Backstage packages: @backstage/backend-common (0.24.1), @backstage/config (0.1.1), @backstage/plugin-catalog-backend (2.0.0), and @backstage/plugin-catalog-common (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant CBMO as catalog-backend-module-openapi
    participant BC as @backstage/backend-common
    participant CFG as @backstage/config
    participant PCB as @backstage/plugin-catalog-backend
    participant PCC as @backstage/plugin-catalog-common
    
    Note over PM,PCC: Dependency Version Update Process
    
    PM->>CBMO: Install dependencies
    
    Note over CBMO: Before: workspace:^ references<br/>After: Fixed versions
    
    CBMO->>BC: Require v0.24.1 (was workspace:^)
    activate BC
    BC-->>CBMO: Provide backend utilities
    deactivate BC
    
    CBMO->>CFG: Require v0.1.1 (was workspace:^)
    activate CFG
    CFG-->>CBMO: Provide configuration
    deactivate CFG
    
    CBMO->>PCB: Require v2.0.0 (was workspace:^)
    activate PCB
    PCB-->>CBMO: Provide catalog backend
    deactivate PCB
    
    CBMO->>PCC: Require v0.1.0 (was workspace:^)
    activate PCC
    PCC-->>CBMO: Provide catalog common
    deactivate PCC
    
    Note over PM,PCC: Dependencies locked to specific versions<br/>for stability and reproducibility

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!