[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0 by snyk-io[bot] · Pull Request #11874 · https-quantumblockchainai-atlassian-net/backstage

snyk-io · 2026-02-07T15:09:28Z

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
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	380
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	380

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:

🦉 Server-side Request Forgery (SSRF)

EntelligenceAI PR Summary

This PR updates the dependency reference for @backstage/integration in the integration-react package from workspace protocol to a fixed version.

Modified packages/integration-react/package.json to use version 0.1.0 instead of workspace:^
Transitions from monorepo workspace dependency to published package dependency
Pins the integration package to a specific version for explicit version control

The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235959 - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235969

codesandbox · 2026-02-07T15:09:33Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

snyk-io · 2026-02-07T15:09:52Z

✅ 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 · 2026-02-07T15:10:17Z

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

Diff	Package	Quality	Maintenance
	@date-io/core@1.3.13
	@types/prop-types@15.7.5
	@types/minimist@1.2.2
	@types/dompurify@2.4.0
	@types/is-glob@4.0.2
	@types/fs-extra@9.0.13
	@types/d3-zoom@3.0.3
	json-schema-traverse@1.0.0
	process@0.11.10
	concat-stream@2.0.0
	@yarnpkg/lockfile@1.1.0
	@types/d3-selection@3.0.5
	@types/jest@29.4.0
	@types/d3-shape@3.1.1
	json-schema-merge-allof@0.8.1
	jss@10.10.0
	@stoplight/types@13.15.0
	yn@5.0.0
	ansi-regex@6.0.1
	js-yaml@4.1.0
	@types/node@16.11.49 ⏵ 20.4.4	⁺¹	⁺¹
	d3-zoom@3.0.0
	d3-shape@3.2.0
	d3-selection@3.0.0
	immer@9.0.21
	git-url-parse@13.1.0
	prop-types@15.8.1
	minimist@1.2.6 ⏵ 1.2.8	⁺¹
	@react-hookz/web@20.1.0
	luxon@2.5.2
See 9 more rows in the dashboard

View full report

socket-security · 2026-02-07T15:10:19Z

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		License policy violation: npm `argparse` under Python-2.0.1 License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE) From: `?` → `npm/js-yaml@4.1.0` → `npm/argparse@2.0.1` ℹ 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/argparse@2.0.1`. 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		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/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.
Warn		License policy violation: npm `typescript` under CC-BY-4.0 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/typescript@5.9.3` ℹ 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@5.9.3`. 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 · 2026-02-07T15:10:42Z

Walkthrough

This pull request modifies the dependency management strategy for the integration-react package by changing how it references the @backstage/integration dependency. The change transitions from using a workspace protocol reference (workspace:^) to a fixed version (0.1.0). This modification indicates a shift from relying on local monorepo workspace dependencies to using a specific published package version. This type of change is typically made when preparing for package publication, resolving version compatibility issues, or establishing more explicit dependency boundaries between packages in the monorepo.

Changes

File(s)	Summary
`packages/integration-react/package.json`	Changed `@backstage/integration` dependency from workspace protocol reference (`workspace:^`) to fixed version `0.1.0`, pinning the package to a specific published version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant NPM as NPM Registry
    participant IntReact as integration-react Package
    participant IntPkg as @backstage/integration

    Note over IntReact,IntPkg: Before: workspace:^ (local monorepo)
    Dev->>IntReact: Build package
    IntReact->>IntPkg: Resolve dependency (workspace)
    Note over IntPkg: Uses local workspace version

    Note over IntReact,IntPkg: After: 0.1.0 (published version)
    Dev->>IntReact: Build package
    IntReact->>NPM: Request @backstage/integration@0.1.0
    NPM-->>IntReact: Return published package
    Note over IntReact: Now uses published version 0.1.0

▶️ ⚡ 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

config - shows the current config
retrigger_review - retriggers the review

More commands to be added soon.

The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235959 - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235969

fix: packages/integration-react/package.json to reduce vulnerabilities

0fb2d9f

The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235959 - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235969

fix: packages/integration-react/package.json to reduce vulnerabilities

0453807

The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235959 - https://snyk.io/vuln/SNYK-JS-WEBPACK-15235969

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0#11874

[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0#11874
snyk-io[bot] wants to merge 2 commits intomasterfrom
snyk-fix-c249fa2a032a5f63d60c47c41dad909d

snyk-io bot commented Feb 7, 2026 •

edited by entelligence-ai-pr-reviews bot

Loading

Uh oh!

codesandbox bot commented Feb 7, 2026

Uh oh!

snyk-io bot commented Feb 7, 2026 •

edited

Loading

Uh oh!

socket-security bot commented Feb 7, 2026 •

edited

Loading

Uh oh!

socket-security bot commented Feb 7, 2026 •

edited

Loading

Uh oh!

entelligence-ai-pr-reviews bot commented Feb 7, 2026

Emoji Descriptions:

Interact with the Bot:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

snyk-io bot commented Feb 7, 2026 • edited by entelligence-ai-pr-reviews bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

Note for zero-installs users

Vulnerabilities that will be fixed with an upgrade:

EntelligenceAI PR Summary

Uh oh!

codesandbox bot commented Feb 7, 2026

Review or Edit in CodeSandbox

Uh oh!

snyk-io bot commented Feb 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Snyk checks have passed. No issues have been found so far.

Uh oh!

socket-security bot commented Feb 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Feb 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

entelligence-ai-pr-reviews bot commented Feb 7, 2026

Walkthrough

Changes

Sequence Diagram

Emoji Descriptions:

Interact with the Bot:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

snyk-io bot commented Feb 7, 2026 •

edited by entelligence-ai-pr-reviews bot

Loading

snyk-io bot commented Feb 7, 2026 •

edited

Loading

socket-security bot commented Feb 7, 2026 •

edited

Loading

socket-security bot commented Feb 7, 2026 •

edited

Loading