[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/badges-backend/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 updates dependency versions in the badges-backend plugin to lock specific versions and upgrade external packages.

• Changed @backstage/backend-common from workspace protocol to 0.24.1
• Changed @backstage/catalog-model from workspace protocol to 0.1.1
• Changed @backstage/plugin-auth-node from workspace protocol to 0.6.0
• Upgraded express from ^4.17.1 to ^4.22.0
• Upgraded supertest from ^6.3.3 to ^7.1.3

[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 dependency versions in the badges-backend plugin's package.json. The changes migrate three Backstage internal dependencies from workspace protocol to fixed versions, ensuring version stability across the plugin. The @backstage/backend-common is updated to 0.24.1, @backstage/catalog-model to 0.1.1, and @backstage/plugin-auth-node to 0.6.0. Additionally, two external dependencies are upgraded: express is bumped from ^4.17.1 to ^4.22.0, and supertest from ^6.3.3 to ^7.1.3. These updates likely address security vulnerabilities and improve package stability by locking to specific versions.

Changes

File(s)	Summary
plugins/badges-backend/package.json	Updated Backstage internal dependencies from workspace protocol to fixed versions: @backstage/backend-common to 0.24.1, @backstage/catalog-model to 0.1.1, and @backstage/plugin-auth-node to 0.6.0. Upgraded external dependencies: express from ^4.17.1 to ^4.22.0 and supertest from ^6.3.3 to ^7.1.3.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client
    participant Express as Express Router
    participant BadgesBackend as Badges Backend Plugin
    participant AuthNode as Auth Node Plugin
    participant CatalogClient as Catalog Client
    participant Database as Database (Knex)

    Note over BadgesBackend: Dependencies Updated:<br/>backend-common: 0.24.1<br/>catalog-model: 0.1.1<br/>auth-node: 0.6.0<br/>express: 4.22.0

    Client->>Express: GET /badges/:entityRef
    Express->>BadgesBackend: Route request
    BadgesBackend->>AuthNode: Authenticate request
    AuthNode-->>BadgesBackend: Auth result
    
    alt Authenticated
        BadgesBackend->>CatalogClient: Fetch entity metadata
        CatalogClient-->>BadgesBackend: Entity data
        BadgesBackend->>Database: Query badge data
        Database-->>BadgesBackend: Badge records
        BadgesBackend->>BadgesBackend: Generate badge (badge-maker)
        BadgesBackend-->>Express: Badge SVG response
        Express-->>Client: Return badge
    else Not authenticated
        BadgesBackend-->>Express: 401 Unauthorized
        Express-->>Client: Error response
    end

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!