Skip to content

[Snyk] Security upgrade @backstage/cli-common from 0.0.0-use.local to 0.1.1#11599

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

[Snyk] Security upgrade @backstage/cli-common from 0.0.0-use.local to 0.1.1#11599
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-f761ce26eadd71195c822ff55e54e287

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 1, 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/create-app/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 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:

🦉 Directory Traversal


EntelligenceAI PR Summary

This PR pins the @backstage/cli-common dependency to version 0.1.1 in the create-app package, replacing the workspace protocol reference.

  • Changed dependency version from workspace:^ to 0.1.1 in packages/create-app/package.json
  • Ensures consistent dependency resolution across different environments
  • Prepares the package for publication outside the monorepo context

@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

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 1, 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 automates a critical security update for the @backstage/cli-common package. The primary goal is to mitigate several vulnerabilities, including Directory Traversal and Uncontrolled Recursion, by upgrading the package version. This ensures the project maintains a secure dependency chain and protects against known exploits.

Highlights

  • Security Upgrade: Upgraded the @backstage/cli-common dependency from 0.0.0-use.local to 0.1.1 to address three vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
  • Automated Remediation: This pull request was automatically generated by Snyk to apply the necessary security fixes.
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.

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 upgrading the @backstage/cli-common package. However, the proposed change replaces the workspace:^ specifier with a pinned version (0.1.1), which is not ideal for this monorepo structure. This change would pin the dependency to an older version than what is available in the workspace (0.1.12) and could lead to dependency conflicts. My review includes a comment to revert this change and stick with the workspace:^ protocol to maintain consistency within the monorepo. After reverting, you will need to run yarn install to update the lockfile, which should properly resolve the vulnerabilities.

},
"dependencies": {
"@backstage/cli-common": "workspace:^",
"@backstage/cli-common": "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 change incorrectly replaces the yarn workspace protocol workspace:^ with a pinned version 0.1.1. In a monorepo setup like this, using workspace:^ is crucial to ensure that the local package from the workspace is used. The version of @backstage/cli-common in this workspace is 0.1.12, which is newer than the pinned version 0.1.1. Pinning to an older, specific version can break the dependency consistency within the monorepo and prevent you from getting the latest updates and fixes from the local package. It is recommended to keep using workspace:^ and run yarn install to update the yarn.lock file, which should resolve the security vulnerabilities correctly by using the workspace's version.

Suggested change
"@backstage/cli-common": "0.1.1",
"@backstage/cli-common": "workspace:^",

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

Walkthrough

This pull request updates the dependency management for the @backstage/cli-common package in the create-app package. The change transitions from using a workspace protocol reference to a pinned version number (0.1.1). This modification ensures consistent dependency resolution across different environments and typically indicates preparation for package publication. By replacing the flexible workspace reference with an explicit version, the package becomes more portable and suitable for distribution outside the monorepo context.

Changes

File(s) Summary
packages/create-app/package.json Updated @backstage/cli-common dependency from workspace protocol reference (workspace:^) to pinned version 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as create-app package.json
    participant NPM as NPM Registry
    participant CLI as @backstage/cli-common

    Note over Dev,CLI: Dependency Version Change

    Dev->>PKG: Update dependency reference
    Note over PKG: Change from workspace:^<br/>to version 0.1.1
    
    Dev->>NPM: Publish/Install
    NPM->>CLI: Resolve @backstage/cli-common@0.1.1
    CLI-->>NPM: Return published package
    NPM-->>PKG: Install dependency
    
    Note over PKG,CLI: Now references published version<br/>instead of local workspace
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