Skip to content

[Snyk] Fix for 4 vulnerabilities#11609

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-5eccc18999994ed69b980139cc6400ab
Closed

[Snyk] Fix for 4 vulnerabilities#11609
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-5eccc18999994ed69b980139cc6400ab

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 1, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/app-defaults/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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  61  
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  45  

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)
🦉 Directory Traversal


EntelligenceAI PR Summary

This PR transitions Backstage dependencies in the app-defaults package from workspace protocol references to explicit version numbers.

  • Changed @backstage/core-app-api from workspace:^ to version 0.1.0
  • Changed @backstage/core-components from workspace:^ to version 0.8.6
  • Changed @backstage/theme from workspace:^ to version 0.1.1
  • Indicates shift from monorepo workspace dependencies to published package versions

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 1, 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 aims to enhance the project's security by resolving four identified medium-severity vulnerabilities. It achieves this by upgrading specific @backstage dependencies to their patched versions within the packages/app-defaults/package.json file, as automatically suggested by Snyk.

Highlights

  • Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses four medium-severity security vulnerabilities, including Directory Traversal, Regular Expression Denial of Service (ReDoS), and Uncontrolled Recursion.
  • Dependency Updates: The fix involves upgrading @backstage/core-app-api to 0.1.0, @backstage/core-components to 0.8.6, and @backstage/theme to 0.1.1 in packages/app-defaults/package.json.
  • Manual Intervention Required: A warning is present indicating that the yarn.lock file was not updated by Snyk and requires manual updating before merging, especially for projects utilizing Yarn's zero-install feature.
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 1, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 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, attempts to fix security vulnerabilities by changing dependency versions. However, the proposed changes are incorrect for this monorepo setup. It replaces workspace: package versions with hardcoded, significantly older versions, which will break the build and cause major inconsistencies. For example, @backstage/core-app-api is downgraded from 1.9.1-next.0 to 0.1.0. The warning in the PR description about failing to update yarn.lock further indicates that the automated process is not compatible with this project's structure. This PR should be closed, and the vulnerabilities should be addressed manually, likely by updating the transitive dependencies that contain them.

Comment on lines +35 to +36
"@backstage/core-app-api": "0.1.0",
"@backstage/core-components": "0.8.6",
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 dependencies should use the workspace:^ protocol to ensure they use the local packages from the monorepo. Pinning to old, fixed versions will cause build failures and inconsistencies. For example, @backstage/core-app-api is being downgraded from a local 1.9.1-next.0 to a published 0.1.0.

Suggested change
"@backstage/core-app-api": "0.1.0",
"@backstage/core-components": "0.8.6",
"@backstage/core-app-api": "workspace:^",
"@backstage/core-components": "workspace:^",

"@backstage/core-plugin-api": "workspace:^",
"@backstage/plugin-permission-react": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "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

This dependency should also use the workspace:^ protocol. Pinning @backstage/theme to 0.1.1 is a significant downgrade from the monorepo version 0.4.1 and will likely cause issues.

Suggested change
"@backstage/theme": "0.1.1",
"@backstage/theme": "workspace:^",

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

Walkthrough

This PR updates the dependency management strategy for the app-defaults package by replacing workspace protocol references with explicit version numbers for three Backstage packages. The changes convert @backstage/core-app-api, @backstage/core-components, and @backstage/theme from workspace-relative dependencies (workspace:^) to specific published versions (0.1.0, 0.8.6, and 0.1.1 respectively). This modification suggests a transition from monorepo workspace dependency resolution to using published package versions, which typically occurs during package publishing workflows or when establishing more explicit version control for external consumption.

Changes

File(s) Summary
packages/app-defaults/package.json Updated three Backstage dependencies from workspace protocol (workspace:^) to explicit versions: @backstage/core-app-api to 0.1.0, @backstage/core-components to 0.8.6, and @backstage/theme to 0.1.1.

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 AppDefaults as app-defaults

    Dev->>PM: npm install
    PM->>AppDefaults: Read package.json
    Note over AppDefaults: Dependencies now use<br/>fixed versions instead of<br/>workspace references
    PM->>Registry: Fetch @backstage/core-app-api@0.1.0
    Registry-->>PM: Return package
    PM->>Registry: Fetch @backstage/core-components@0.8.6
    Registry-->>PM: Return package
    PM->>Registry: Fetch @backstage/theme@0.1.1
    Registry-->>PM: Return package
    PM->>AppDefaults: Install 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

github-actions Bot commented Feb 8, 2026

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 8, 2026
@github-actions github-actions Bot closed this Mar 12, 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