Skip to content

[Snyk] Fix for 2 vulnerabilities#12440

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-14c0868e21e6883efb388042dadb8823
Closed

[Snyk] Fix for 2 vulnerabilities#12440
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-14c0868e21e6883efb388042dadb8823

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 16, 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/devtools-backend/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

Updated dependency version specifications in devtools-backend plugin package.json, transitioning from workspace protocol to explicit versioning.

  • Replaced workspace:^ references with pinned versions for 6 Backstage packages
  • Pinned @backstage/backend-common to 0.24.1
  • Pinned @backstage/backend-plugin-api, @backstage/plugin-auth-node, @backstage/plugin-devtools-common, and @backstage/plugin-permission-node to 0.1.0
  • Pinned @backstage/config-loader to 0.1.1
  • Upgraded express dependency from ^4.18.1 to ^4.22.0

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 16, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown

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

@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 updating key dependencies within the plugins/devtools-backend package. The updates target specific versions of @backstage packages and express to mitigate identified high and medium severity vulnerabilities, ensuring a more secure and stable application environment.

Highlights

  • Vulnerability Fixes: This pull request addresses two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
  • Dependency Updates: Several yarn dependencies within the plugins/devtools-backend package have been updated to newer versions to remediate the identified vulnerabilities, including various @backstage packages and express.
  • Manual yarn.lock Update Required: The yarn.lock file was not automatically updated by Snyk and requires manual intervention to ensure consistency and proper dependency resolution, especially for projects utilizing Yarn's zero-installs feature.
Changelog
  • plugins/devtools-backend/package.json
    • Updated @backstage/backend-common from workspace:^ to 0.24.1.
    • Updated @backstage/backend-plugin-api from workspace:^ to 0.1.0.
    • Updated @backstage/config-loader from workspace:^ to 0.1.1.
    • Updated @backstage/plugin-auth-node from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-devtools-common from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-permission-node from workspace:^ to 0.1.0.
    • Updated express from ^4.18.1 to ^4.22.0.
Activity
  • Snyk automatically created this pull request to address identified security vulnerabilities.
  • A warning was issued indicating that the yarn.lock file failed to update and requires manual attention.
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.

@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 atob under CC-BY-3.0

License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS)

From: ?npm/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.

View full report

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

Walkthrough

This PR updates the devtools-backend plugin's dependency management by replacing workspace protocol references with explicit version numbers for all Backstage packages. The changes pin specific versions for backend-common (0.24.1), backend-plugin-api (0.1.0), config-loader (0.1.1), auth-node (0.1.0), devtools-common (0.1.0), and permission-node (0.1.0). Additionally, the express dependency is upgraded from version 4.18.1 to 4.22.0. This transition from workspace references to explicit versioning suggests preparation for package publication or implementation of stricter dependency version control for improved stability and reproducibility.

Changes

File(s) Summary
plugins/devtools-backend/package.json Replaced workspace protocol references (workspace:^) with explicit version numbers for six Backstage packages (@backstage/backend-common: 0.24.1, @backstage/backend-plugin-api: 0.1.0, @backstage/config-loader: 0.1.1, @backstage/plugin-auth-node: 0.1.0, @backstage/plugin-devtools-common: 0.1.0, @backstage/plugin-permission-node: 0.1.0) and upgraded express from ^4.18.1 to ^4.22.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant App as Backstage App
    participant DevTools as DevTools Backend Plugin
    participant Config as Config Loader
    participant Auth as Auth Node
    participant Permissions as Permission Node
    participant Express as Express Router
    participant Backend as Backend Common

    App->>DevTools: Initialize Plugin (v0.1.0)
    activate DevTools
    
    DevTools->>Config: Load Configuration (v0.1.1)
    activate Config
    Config-->>DevTools: Return Config
    deactivate Config
    
    DevTools->>Backend: Setup Backend Services (v0.24.1)
    activate Backend
    Backend-->>DevTools: Services Ready
    deactivate Backend
    
    DevTools->>Auth: Initialize Auth (v0.1.0)
    activate Auth
    Auth-->>DevTools: Auth Ready
    deactivate Auth
    
    DevTools->>Permissions: Setup Permissions (v0.1.0)
    activate Permissions
    Permissions-->>DevTools: Permissions Ready
    deactivate Permissions
    
    DevTools->>Express: Create Routes (v4.22.0)
    activate Express
    Express-->>DevTools: Router Ready
    deactivate Express
    
    DevTools-->>App: Plugin Initialized
    deactivate DevTools
    
    Note over DevTools,Express: Updated dependencies:<br/>- Express 4.18.1 → 4.22.0<br/>- Backend packages to specific versions
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 from Snyk aims to fix two security vulnerabilities by updating dependencies. However, there are critical issues with the proposed changes. Several internal @backstage packages are incorrectly changed from workspace: references to pinned versions, which breaks the monorepo workflow. Additionally, the express package is updated to a non-existent version. These changes will prevent the project from building. I've added specific comments with suggestions to fix these issues. Please also remember to update the yarn.lock file after applying the corrections, as noted in the PR description.

Comment on lines +25 to +34
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.1.0",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-devtools-common": "workspace:^",
"@backstage/plugin-auth-node": "0.1.0",
"@backstage/plugin-devtools-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-permission-node": "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

Replacing workspace:^ with pinned versions for these internal packages is incorrect for a monorepo. It breaks the local development workflow by fetching packages from the registry instead of the local workspace. These changes should be reverted.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.1.0",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-devtools-common": "workspace:^",
"@backstage/plugin-auth-node": "0.1.0",
"@backstage/plugin-devtools-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-permission-node": "0.1.0",
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-devtools-common": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",

"@yarnpkg/lockfile": "^1.1.0",
"@yarnpkg/parsers": "^3.0.0-rc.4",
"express": "^4.18.1",
"express": "^4.22.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

The express package version is being updated to ^4.22.0, but this version does not exist in the npm registry. The latest version of express is 4.19.2. This will cause yarn install to fail. Please use a valid and existing version. Using ^4.19.2 should resolve the qs vulnerability.

Suggested change
"express": "^4.22.0",
"express": "^4.19.2",

@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 23, 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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants