Skip to content

[Snyk] Fix for 4 vulnerabilities#10600

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-56f99e67b99e0c99902005d4af993a8b
Closed

[Snyk] Fix for 4 vulnerabilities#10600
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-56f99e67b99e0c99902005d4af993a8b

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jan 23, 2026

snyk-top-banner

Snyk has created this PR to fix 4 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
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  590  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  550  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  545  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  545  

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)
🦉 Prototype Pollution


EntelligenceAI PR Summary

This PR pins Backstage dependencies to explicit versions in the lighthouse-backend plugin package.json, replacing workspace protocol references.

  • Updated @backstage/backend-common to version 0.24.1
  • Updated @backstage/backend-plugin-api to version 1.6.1
  • Updated @backstage/catalog-client to version 0.2.0
  • Updated @backstage/config to version 0.1.1
  • Updated @backstage/plugin-catalog-node to version 1.13.0
  • Updated @backstage/plugin-lighthouse-common to version 0.1.0
  • Indicates transition from monorepo workspace dependency management to pinned versions for release preparation or dependency stabilization

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 23, 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 Jan 23, 2026

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.

@socket-security
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.8.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR transitions the lighthouse-backend plugin from workspace protocol dependency references to explicit version pinning. Six Backstage packages are updated with specific version numbers: backend-common (0.24.1), backend-plugin-api (1.6.1), catalog-client (0.2.0), config (0.1.1), plugin-catalog-node (1.13.0), and plugin-lighthouse-common (0.1.0). This change represents a shift from monorepo workspace dependency management to fixed version specifications, typically performed during package release preparation or to ensure dependency stability across environments.

Changes

File(s) Summary
plugins/lighthouse-backend/package.json Replaced workspace protocol references with explicit version numbers for six Backstage dependencies: @backstage/backend-common (0.24.1), @backstage/backend-plugin-api (1.6.1), @backstage/catalog-client (0.2.0), @backstage/config (0.1.1), @backstage/plugin-catalog-node (1.13.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 Config as @backstage/config
    participant CatalogClient as @backstage/catalog-client
    participant CatalogNode as @backstage/plugin-catalog-node
    participant BackendAPI as @backstage/backend-plugin-api
    participant Common as @backstage/backend-common
    
    Note over LH: Plugin Initialization<br/>(using updated dependencies)
    
    Client->>LH: Request Lighthouse audit
    activate LH
    
    LH->>Config: Load configuration
    Config-->>LH: Return config settings
    
    LH->>CatalogClient: Fetch entity details
    activate CatalogClient
    CatalogClient-->>LH: Return entity metadata
    deactivate CatalogClient
    
    LH->>CatalogNode: Process catalog entity
    activate CatalogNode
    CatalogNode-->>LH: Return processed data
    deactivate CatalogNode
    
    LH->>BackendAPI: Register plugin routes
    BackendAPI-->>LH: Routes registered
    
    LH->>Common: Use backend utilities
    Common-->>LH: Utility response
    
    LH-->>Client: Return audit results
    deactivate LH
    
    Note over LH,Common: All dependencies now use<br/>fixed versions instead of workspace:^
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

github-actions Bot commented Apr 2, 2026

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 Apr 2, 2026
@github-actions github-actions Bot closed this Apr 7, 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.

0 participants