Skip to content

[Snyk] Security upgrade @backstage/integration-react from 0.0.0-use.local to 0.1.1#5394

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

[Snyk] Security upgrade @backstage/integration-react from 0.0.0-use.local to 0.1.1#5394
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-fa430986801a9de94e8a2c5e95a7d5c0

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jun 4, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/github-deployments/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 Improper Link Resolution Before File Access ('Link Following')
SNYK-JS-TARFS-10293725
  721  

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:

🦉 Improper Link Resolution Before File Access ('Link Following')

Summary by Sourcery

Upgrade @backstage/integration-react to version 0.1.1 to fix a critical security vulnerability

Bug Fixes:

  • Resolve high severity Improper Link Resolution Before File Access (Link Following) vulnerability (SNYK-JS-TARFS-10293725) by upgrading @backstage/integration-react

Enhancements:

  • Upgrade @backstage/integration-react from workspace local version to 0.1.1

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jun 4, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Jun 4, 2025

Reviewer's Guide

This PR upgrades the @backstage/integration-react dependency in the GitHub Deployments plugin from a local workspace reference to a fixed release (0.1.1) to remediate a high-severity tarfs vulnerability.

Flow Diagram: Snyk's Automated Dependency Update and PR Process

graph TD
    A["Snyk scans 'yarn' project dependencies"] --> B{"Identifies vulnerable @backstage/integration-react<br/>(SNYK-JS-TARFS-10293725)"};
    B --> C["Determines fix: Upgrade to version 0.1.1"];
    C --> D["Snyk automatically creates a Pull Request"];
    D --> E["PR modifies 'plugins/github-deployments/package.json':<br/>- @backstage/integration-react: workspace:^<br/>+ @backstage/integration-react: 0.1.1"];
    E --> F["Developer reviews PR<br/>(Note: Snyk warns 'Failed to update yarn.lock, please update manually')"];
    F --> G["Developer manually updates yarn.lock and merges PR"];
    G --> H["Vulnerability remediated"];
Loading

File-Level Changes

Change Details Files
Pin @backstage/integration-react to a released version
  • Replaced workspace:^ reference with version 0.1.1
  • Removes local workspace linkage to pull in patched code
plugins/github-deployments/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jun 4, 2025

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

security/snyk check is complete. No issues have been found. (View Details)

@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 for details)
Warn High
atob@2.1.2 has a License Policy Violation.

License: CC-BY-3.0 (package/LICENSE.DOCS)

From: storybook/yarn.locknpm/atob@2.1.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/atob@2.1.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
caniuse-lite@1.0.30001378 has a License Policy Violation.

License: CC-BY-4.0 (npm metadata)

License: CC-BY-4.0 (package/LICENSE)

License: CC-BY-4.0 (package/package.json)

From: microsite/yarn.locknpm/caniuse-lite@1.0.30001378

ℹ 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/caniuse-lite@1.0.30001378. 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
polished@4.2.2 has a License Policy Violation.

License: OFL-1.1 (package/docs/assets/fonts/LICENSE.txt)

From: storybook/yarn.locknpm/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.

View full report

"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change introduces a potential dependency management issue by replacing the workspace reference (workspace:^) with a fixed version (0.1.1) from an external registry. In a monorepo structure, this inconsistency can lead to:

  1. Version conflicts when multiple components require different versions of the same package
  2. Duplicate package installations increasing bundle size
  3. Potential runtime compatibility issues

To address the security vulnerability while maintaining monorepo integrity, consider:

  • Updating the vulnerable dependency within your workspace
  • Ensuring all @backstage packages use consistent reference patterns

The security fix is important, but implementing it in a way that preserves the monorepo's dependency management approach will prevent future integration problems.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@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 Jun 11, 2025
@github-actions github-actions Bot closed this Jun 18, 2025
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