Skip to content

[Snyk] Fix for 3 vulnerabilities#12045

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-80b99957301815002b2a1906f06039b1
Closed

[Snyk] Fix for 3 vulnerabilities#12045
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-80b99957301815002b2a1906f06039b1

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/test-utils/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
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  83  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  83  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  62  

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR converts workspace protocol dependencies to fixed version dependencies in the test-utils package.

  • Changed @backstage/config from workspace:^ to fixed version 0.1.1
  • Changed @backstage/core-plugin-api from workspace:^ to fixed version 0.1.0
  • Changed @backstage/plugin-permission-react from workspace:^ to fixed version 0.1.0
  • Indicates transition from monorepo workspace references to explicit version pinning

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by resolving three identified vulnerabilities. It achieves this by updating specific package dependencies to their patched versions, ensuring the application is protected against known security flaws.

Highlights

  • Vulnerability Fixes: Addressed 3 security vulnerabilities identified by Snyk: two Server-side Request Forgery (SSRF) issues and one Allocation of Resources Without Limits or Throttling issue.
  • Dependency Updates: Updated @backstage/config, @backstage/core-plugin-api, and @backstage/plugin-permission-react dependencies in packages/test-utils/package.json to specific, patched versions.
  • Yarn Zero-Installs Guidance: Provided a note for Yarn zero-installs users, advising them to run yarn to update the .yarn/cache/ directory, as this PR does not automatically update it.
  • Manual yarn.lock Update Required: Included a warning indicating that the yarn.lock file failed to update automatically and requires manual intervention before merging.
Changelog
  • packages/test-utils/package.json
    • Updated @backstage/config from workspace:^ to 0.1.1.
    • Updated @backstage/core-plugin-api from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-permission-react from workspace:^ to 0.1.0.
Activity
  • This pull request was automatically created by Snyk to address security vulnerabilities.
  • A warning was noted that the yarn.lock file failed to update and requires manual intervention.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by updating dependencies. However, the proposed changes significantly downgrade several @backstage packages, replacing workspace: pointers with very old, pinned versions. This will almost certainly break the build and introduce many more issues than it solves. These changes should be rejected, and the dependencies should be updated manually to appropriate, newer versions that resolve the vulnerabilities without causing major regressions.

Comment on lines +48 to +52
"@backstage/config": "0.1.1",
"@backstage/core-app-api": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/core-plugin-api": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-react": "workspace:^",
"@backstage/plugin-permission-react": "0.1.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

These dependency changes appear to be incorrect. They are downgrading packages to very old versions and removing the workspace: specifier, which is likely to break the build and cause regressions. The warning in the PR description 'Failed to update the yarn.lock, please update manually before merging' is another strong indicator that these changes are problematic. For example:

  • @backstage/config is being downgraded from a workspace version (likely 1.0.8 based on the changelog) to 0.1.1.
  • @backstage/core-plugin-api is being downgraded from a workspace version (likely 1.5.3) to 0.1.0.
  • @backstage/plugin-permission-react is being downgraded from a workspace version (likely 0.4.14) to 0.1.0.

These automated changes from Snyk seem to be faulty. I suggest reverting these changes. The vulnerabilities should be addressed by upgrading to compatible versions, not by performing major downgrades.

    "@backstage/config": "workspace:^",
    "@backstage/core-app-api": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/plugin-permission-common": "workspace:^",
    "@backstage/plugin-permission-react": "workspace:^"

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

Walkthrough

This PR updates the dependency management strategy for the test-utils package by converting workspace protocol references to fixed version dependencies. Three Backstage packages that were previously referenced using the monorepo workspace protocol (workspace:^) are now pinned to specific versions: @backstage/config to version 0.1.1, @backstage/core-plugin-api to version 0.1.0, and @backstage/plugin-permission-react to version 0.1.0. This change suggests a shift in the package's dependency management approach, potentially in preparation for publishing the package independently or establishing more explicit version control over its dependencies.

Changes

File(s) Summary
packages/test-utils/package.json Converted three workspace dependencies to fixed versions: @backstage/config to 0.1.1, @backstage/core-plugin-api to 0.1.0, and @backstage/plugin-permission-react to 0.1.0, replacing workspace:^ protocol references.

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 TU as test-utils Package

    Dev->>PM: Install dependencies for test-utils
    PM->>TU: Read package.json
    
    Note over TU,PM: Dependency Resolution Changes
    
    alt @backstage/config
        PM->>NPM: Fetch version 0.1.1
        Note right of PM: Changed from workspace:^<br/>to pinned version
        NPM-->>PM: Return package
    end
    
    alt @backstage/core-plugin-api
        PM->>NPM: Fetch version 0.1.0
        Note right of PM: Changed from workspace:^<br/>to pinned version
        NPM-->>PM: Return package
    end
    
    alt @backstage/plugin-permission-react
        PM->>NPM: Fetch version 0.1.0
        Note right of PM: Changed from workspace:^<br/>to pinned version
        NPM-->>PM: Return package
    end
    
    alt Other workspace dependencies
        PM->>WS: Resolve workspace:^ references
        Note right of PM: Remaining deps still use<br/>workspace protocol
        WS-->>PM: Return local packages
    end
    
    PM->>TU: Install all resolved dependencies
    PM-->>Dev: Installation complete
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 Feb 20, 2026
@github-actions github-actions Bot closed this Mar 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.

2 participants