Skip to content

[Snyk] Fix for 3 vulnerabilities#11626

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-43a9547e06326f0633b7086588b8e122
Closed

[Snyk] Fix for 3 vulnerabilities#11626
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-43a9547e06326f0633b7086588b8e122

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 2, 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/backend-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
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 replaces workspace protocol references with explicit version numbers for Backstage dependencies in the backend-test-utils package.

  • Changed @backstage/backend-app-api from workspace protocol to version 0.5.0
  • Changed @backstage/backend-plugin-api from workspace protocol to version 0.6.19
  • Changed @backstage/config from workspace protocol to version 0.1.1
  • Changed @backstage/plugin-auth-node from workspace protocol to version 0.6.0
  • Ensures version consistency and prepares package for independent publishing

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 2, 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 2, 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 bolster the project's security by resolving three medium-severity vulnerabilities found in its yarn dependencies. The fix involves updating specific @backstage packages within the packages/backend-test-utils/package.json file. Reviewers should be aware of the necessary manual steps for yarn.lock and zero-install users to fully integrate these security updates.

Highlights

  • Vulnerability Fixes: This pull request addresses 3 identified vulnerabilities in the project's yarn dependencies: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
  • Dependency Upgrades: Several @backstage dependencies in packages/backend-test-utils/package.json have been upgraded to newer versions to mitigate the identified vulnerabilities. Specifically, @backstage/backend-app-api is updated to 0.5.0, @backstage/backend-plugin-api to 0.6.19, @backstage/config to 0.1.1, and @backstage/plugin-auth-node to 0.6.0.
  • Yarn Zero-Install Consideration: Users leveraging Yarn's zero-install feature should note that this PR does not update the .yarn/cache/ directory. A manual yarn command execution is required to update the cache and ensure proper development setup.
  • Manual yarn.lock Update Required: Snyk reported a failure to automatically update the yarn.lock file. This file will need to be manually updated before merging this pull request to ensure dependency consistency.
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.

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

Walkthrough

This pull request updates the dependency management strategy for the backend-test-utils package by replacing workspace protocol references with explicit version numbers for four Backstage packages. The changes pin @backstage/backend-app-api to version 0.5.0, @backstage/backend-plugin-api to 0.6.19, @backstage/config to 0.1.1, and @backstage/plugin-auth-node to 0.6.0. This modification ensures version consistency across different environments and likely prepares the package for independent publishing by removing workspace-relative versioning dependencies.

Changes

File(s) Summary
packages/backend-test-utils/package.json Updated four Backstage dependencies from workspace protocol references to explicit version numbers: @backstage/backend-app-api to 0.5.0, @backstage/backend-plugin-api to 0.6.19, @backstage/config to 0.1.1, and @backstage/plugin-auth-node to 0.6.0.

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 BT as backend-test-utils

    Dev->>PM: npm install / yarn install
    PM->>BT: Read package.json dependencies
    Note over BT: Dependencies changed from<br/>workspace:^ to fixed versions
    
    alt backend-app-api
        PM->>Registry: Fetch @backstage/backend-app-api@0.5.0
        Registry-->>PM: Return package
    else backend-plugin-api
        PM->>Registry: Fetch @backstage/backend-plugin-api@0.6.19
        Registry-->>PM: Return package
    else config
        PM->>Registry: Fetch @backstage/config@0.1.1
        Registry-->>PM: Return package
    else plugin-auth-node
        PM->>Registry: Fetch @backstage/plugin-auth-node@0.6.0
        Registry-->>PM: Return package
    end
    
    PM->>BT: Install resolved dependencies
    PM-->>Dev: Installation complete
    
    Note over Dev,BT: Dependencies now pinned to<br/>specific versions instead of<br/>workspace references
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

The pull request correctly identifies and attempts to fix three vulnerabilities by updating several @backstage dependencies to their patched versions. However, the PR description explicitly states that the yarn.lock file was not updated. It is crucial to manually update yarn.lock to ensure these security fixes are properly applied and the project uses the intended secure dependency versions. Failure to do so will leave the vulnerabilities unaddressed.

},
"dependencies": {
"@backstage/backend-app-api": "workspace:^",
"@backstage/backend-app-api": "0.5.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 PR description indicates that yarn.lock was not updated. For these dependency updates to effectively mitigate the reported vulnerabilities, it is critical to run yarn install (or yarn if zero-installs is enabled) to regenerate and commit the yarn.lock file. Without this step, the project might still be using the vulnerable versions of these packages, leaving the security issues unaddressed.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 9, 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 9, 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