Skip to content

[Snyk] Fix for 2 vulnerabilities#12210

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-ff7e2b003b0814c5351e20b9b4ba9055
Closed

[Snyk] Fix for 2 vulnerabilities#12210
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-ff7e2b003b0814c5351e20b9b4ba9055

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 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/scaffolder-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
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  157  
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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling


EntelligenceAI PR Summary

Updates dependency versions in the scaffolder-react plugin package.json for improved stability and bug fixes.

  • Pinned @backstage/plugin-catalog-react to exact version 0.0.1
  • Pinned @backstage/types to exact version 0.1.1
  • Upgraded 'qs' package from ^6.9.4 to ^6.14.2
  • Replaced workspace protocol with specific version numbers for internal dependencies

@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 security posture of the project by upgrading several dependencies within plugins/scaffolder-react/package.json. The updates specifically target and resolve two identified vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) and a medium-severity Allocation of Resources Without Limits or Throttling issue.

Highlights

  • Security Vulnerability Fixes: Upgraded qs dependency from ^6.9.4 to ^6.14.2 to address a medium-severity "Allocation of Resources Without Limits or Throttling" vulnerability (SNYK-JS-QS-15268416).
  • Security Vulnerability Fixes: Updated @backstage/plugin-catalog-react from workspace:^ to 0.0.1 and @backstage/types from workspace:^ to 0.1.1 to resolve a high-severity "Regular Expression Denial of Service (ReDoS)" vulnerability (SNYK-JS-AJV-15274295).
  • Manual Intervention Required: Included a warning that the yarn.lock file failed to update and requires manual intervention before merging, particularly for projects utilizing Yarn's zero-installs feature.
Changelog
  • plugins/scaffolder-react/package.json
    • Updated qs dependency from ^6.9.4 to ^6.14.2.
    • Updated @backstage/plugin-catalog-react from workspace:^ to 0.0.1.
    • Updated @backstage/types from workspace:^ to 0.1.1.
Activity
  • An automated pull request was created by Snyk to address two security vulnerabilities.
  • A warning was issued regarding the failure to update yarn.lock, advising 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.

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

Walkthrough

This PR updates dependency management in the scaffolder-react plugin's package.json file. The changes include pinning two internal Backstage workspace dependencies to specific versions instead of using the workspace protocol, and upgrading the 'qs' package to a newer minor version. These modifications improve dependency stability by locking internal packages to exact versions and incorporate bug fixes and improvements from the updated 'qs' library.

Changes

File(s) Summary
plugins/scaffolder-react/package.json Pinned @backstage/plugin-catalog-react to version 0.0.1 and @backstage/types to version 0.1.1, replacing workspace protocol references. Upgraded 'qs' package from ^6.9.4 to ^6.14.2.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    participant Build as Build System
    participant App as Scaffolder React Plugin

    Dev->>PM: Update package.json dependencies
    Note over Dev,PM: Change catalog-react to 0.0.1<br/>Change types to 0.1.1<br/>Upgrade qs to ^6.14.2
    
    Dev->>PM: Run install command
    activate PM
    
    PM->>Registry: Resolve @backstage/plugin-catalog-react@0.0.1
    Registry-->>PM: Return package metadata
    
    PM->>Registry: Resolve @backstage/types@0.1.1
    Registry-->>PM: Return package metadata
    
    PM->>Registry: Resolve qs@^6.14.2
    Registry-->>PM: Return package metadata
    
    PM->>PM: Install dependencies to node_modules
    deactivate PM
    PM-->>Dev: Dependencies installed
    
    Dev->>Build: Trigger build process
    activate Build
    
    Build->>App: Import catalog-react (v0.0.1)
    Build->>App: Import types (v0.1.1)
    Build->>App: Import qs (v6.14.2)
    
    Build->>Build: Compile and bundle
    deactivate Build
    Build-->>Dev: Build 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.

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 two security vulnerabilities by updating dependencies. The update for the qs package appears correct. However, the changes for @backstage/plugin-catalog-react and @backstage/types are problematic. They replace local workspace dependencies (workspace:^) with old, fixed versions from the public registry. This is incorrect for a monorepo setup and will likely break the project. I've left a specific comment with a suggestion to revert this part of the change. Furthermore, as noted in the PR description, the yarn.lock file has not been updated. This is a required step after any dependency change and must be done manually before this PR can be merged.

Comment on lines +53 to +56
"@backstage/plugin-catalog-react": "0.0.1",
"@backstage/plugin-scaffolder-common": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/types": "workspace:^",
"@backstage/types": "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.

critical

These changes appear to be incorrect for this monorepo setup. Replacing workspace:^ with old, pinned versions for @backstage/plugin-catalog-react and @backstage/types will likely break the build and local development, as it will ignore the local packages in the workspace.

  • @backstage/plugin-catalog-react is being pinned to 0.0.1, which is a significant downgrade.
  • @backstage/types is being pinned to 0.1.1, while the version in the workspace is 1.1.0.

This change should be reverted. The ajv vulnerability that Snyk is trying to fix should be addressed by either updating the direct dependency that brings in the vulnerable version of ajv, or by using a resolutions field in package.json to enforce a secure version of ajv across the workspace.

    "@backstage/plugin-catalog-react": "workspace:^",
    "@backstage/plugin-scaffolder-common": "workspace:^",
    "@backstage/theme": "workspace:^",
    "@backstage/types": "workspace:^"

@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 Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants