Skip to content

[Snyk] Fix for 2 vulnerabilities#12154

Closed
snyk-io[bot] wants to merge 2 commits intomasterfrom
snyk-fix-817918ba1f5ae0184221a0a455063950
Closed

[Snyk] Fix for 2 vulnerabilities#12154
snyk-io[bot] wants to merge 2 commits intomasterfrom
snyk-fix-817918ba1f5ae0184221a0a455063950

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 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/lighthouse-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
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  685  
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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling


EntelligenceAI PR Summary

Updates dependency version specifications in the lighthouse-backend plugin package.json from workspace references to explicit versions.

  • Pins @backstage/backend-common to version 0.24.1
  • Pins @backstage/catalog-client to version 0.2.0
  • Pins @backstage/catalog-model to version 0.1.1
  • Pins @backstage/plugin-catalog-node to version 1.0.0
  • Pins @backstage/plugin-lighthouse-common to version 0.1.0
  • Maintains workspace protocol references for other Backstage dependencies

@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 lighthouse-backend plugin by converting five Backstage package dependencies from workspace protocol references to explicit version numbers. The changes pin specific versions: @backstage/backend-common (0.24.1), @backstage/catalog-client (0.2.0), @backstage/catalog-model (0.1.1), @backstage/plugin-catalog-node (1.0.0), and @backstage/plugin-lighthouse-common (0.1.0). This modification standardizes dependency versions and likely prepares the package for publication or deployment to environments where workspace references are not supported. Other Backstage dependencies continue using workspace protocol references.

Changes

File(s) Summary
plugins/lighthouse-backend/package.json Converted five Backstage package dependencies from workspace protocol references (workspace:^) to explicit version numbers: @backstage/backend-common (0.24.1), @backstage/catalog-client (0.2.0), @backstage/catalog-model (0.1.1), @backstage/plugin-catalog-node (1.0.0), and @backstage/plugin-lighthouse-common (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client as External Client
    participant LH as Lighthouse Backend Plugin
    participant BC as @backstage/backend-common<br/>(v0.24.1)
    participant CC as @backstage/catalog-client<br/>(v0.2.0)
    participant CN as @backstage/plugin-catalog-node<br/>(v1.0.0)
    participant CM as @backstage/catalog-model<br/>(v0.1.1)
    participant LC as @backstage/plugin-lighthouse-common<br/>(v0.1.0)

    Note over LH,LC: Dependency Version Updates<br/>workspace:^ → specific versions

    Client->>LH: Request Lighthouse audit
    activate LH
    
    LH->>BC: Initialize backend services
    activate BC
    BC-->>LH: Service configuration
    deactivate BC
    
    LH->>CC: Fetch catalog entities
    activate CC
    CC->>CM: Validate entity schema
    activate CM
    CM-->>CC: Validated entities
    deactivate CM
    CC-->>LH: Entity list
    deactivate CC
    
    LH->>CN: Process catalog nodes
    activate CN
    CN->>CM: Apply catalog model
    activate CM
    CM-->>CN: Structured data
    deactivate CM
    CN-->>LH: Processed nodes
    deactivate CN
    
    LH->>LC: Use common Lighthouse types/utilities
    activate LC
    LC-->>LH: Shared definitions
    deactivate LC
    
    LH->>LH: Execute Lighthouse audit
    
    LH-->>Client: Audit results
    deactivate LH
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 28, 2026
@github-actions github-actions Bot closed this Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant