Skip to content

[Snyk] Fix for 2 vulnerabilities#10795

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-55a8f5bf3fccca481ff30674d7fdde42
Open

[Snyk] Fix for 2 vulnerabilities#10795
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-55a8f5bf3fccca481ff30674d7fdde42

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io bot commented Jan 26, 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/sonarqube/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  
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  575  

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)
🦉 Directory Traversal


EntelligenceAI PR Summary

This PR locks Backstage dependencies to specific versions in the SonarQube plugin package configuration.

  • Changed @backstage/core-components from workspace:^ to pinned version 0.8.6
  • Changed @backstage/theme from workspace:^ to pinned version 0.1.1
  • Replaces monorepo workspace resolution with explicit version pinning
  • Modified in plugins/sonarqube/package.json

@codesandbox
Copy link
Copy Markdown

codesandbox bot commented Jan 26, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@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

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Jan 26, 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 dependency management for the SonarQube plugin by replacing workspace protocol references with pinned versions for two Backstage packages. The @backstage/core-components dependency is locked to version 0.8.6, and @backstage/theme is locked to version 0.1.1. This change moves away from monorepo workspace resolution to explicit version pinning, which typically indicates a requirement for specific version compatibility or preparation for publishing the plugin as a standalone package outside the monorepo environment.

Changes

File(s) Summary
plugins/sonarqube/package.json Updated dependency versions from workspace protocol (workspace:^) to pinned versions: @backstage/core-components to 0.8.6 and @backstage/theme to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant Package as sonarqube/package.json
    participant Registry as Package Registry
    participant Workspace as Workspace Packages
    
    Note over Package: Dependency version change
    
    Build->>Package: Read dependencies
    
    alt @backstage/core-components
        Package-->>Build: Version: 0.8.6 (pinned)
        Build->>Registry: Fetch @backstage/core-components@0.8.6
        Registry-->>Build: Return package
    end
    
    alt @backstage/theme
        Package-->>Build: Version: 0.1.1 (pinned)
        Build->>Registry: Fetch @backstage/theme@0.1.1
        Registry-->>Build: Return package
    end
    
    alt Other workspace dependencies
        Package-->>Build: Version: workspace:^
        Build->>Workspace: Resolve from local workspace
        Workspace-->>Build: Return local package
    end
    
    Note over Build,Registry: Changed from workspace resolution<br/>to fixed version resolution
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 Mar 28, 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