Skip to content

[Snyk] Fix for 2 vulnerabilities#10909

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-9a95532ca292be65c0be308bc1052e20
Closed

[Snyk] Fix for 2 vulnerabilities#10909
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-9a95532ca292be65c0be308bc1052e20

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):

  • packages/integration-react/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 updates dependency version constraints in the integration-react package from workspace references to explicit pinned versions.

  • Changed @backstage/config from workspace:^ to version 0.1.1
  • Changed @backstage/core-components from workspace:^ to version 0.8.6
  • Changed @backstage/core-plugin-api from workspace:^ to version 0.1.0
  • Changed @backstage/integration from workspace:^ to version 0.1.0
  • Transitions from monorepo workspace dependencies to fixed version pinning for stability and publication readiness

@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

@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.

@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedreact@​17.0.21001007897100
Addedstorybook-dark-mode@​1.1.29910010080100
Addedswc-loader@​0.2.31001009285100
Addedreact-hot-loader@​4.13.19710010085100
Addedtypescript@​4.7.410010010010080
Addedreact-dom@​17.0.21001009098100

View full report

@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 polished under OFL-1.1

License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/docs/assets/fonts/LICENSE.txt)

From: ?npm/@storybook/addon-actions@6.5.16npm/polished@4.2.2

ℹ 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/polished@4.2.2. 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.

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: storybook/package.jsonnpm/typescript@4.7.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.7.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 @backstage/integration-react package from using workspace protocol references to pinned dependency versions. Four Backstage dependencies are updated with explicit version numbers: @backstage/config (0.1.1), @backstage/core-components (0.8.6), @backstage/core-plugin-api (0.1.0), and @backstage/integration (0.1.0). This change replaces the workspace:^ protocol with fixed version constraints, indicating preparation for package publication or establishing stable dependency versions for production use. The modification ensures consistent dependency resolution across different environments and prevents potential version conflicts in downstream consumers.

Changes

File(s) Summary
packages/integration-react/package.json Updated four Backstage dependencies from workspace protocol (workspace:^) to pinned versions: @backstage/config to 0.1.1, @backstage/core-components to 0.8.6, @backstage/core-plugin-api to 0.1.0, and @backstage/integration to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace Registry
    participant NPM as NPM Registry
    participant App as integration-react

    Dev->>PM: npm install / yarn install
    
    Note over PM,App: Before: workspace:^ protocol
    PM->>WS: Resolve workspace dependencies
    WS-->>PM: Return local workspace versions
    PM->>App: Link local packages
    
    Note over PM,NPM: After: Pinned versions (0.1.1, 0.8.6, etc.)
    
    alt Dependency Resolution (New Approach)
        PM->>NPM: Fetch @backstage/config@0.1.1
        NPM-->>PM: Return package
        PM->>NPM: Fetch @backstage/core-components@0.8.6
        NPM-->>PM: Return package
        PM->>NPM: Fetch @backstage/core-plugin-api@0.1.0
        NPM-->>PM: Return package
        PM->>NPM: Fetch @backstage/integration@0.1.0
        NPM-->>PM: Return package
    end
    
    PM->>App: Install pinned versions
    App-->>Dev: Dependencies installed
    
    Note over Dev,App: Result: Consistent versions across environments
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 27, 2026
@github-actions github-actions bot closed this Apr 1, 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