Skip to content

Conversation

@q1blue
Copy link

@q1blue q1blue commented Jan 31, 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):

  • code/frameworks/react-vite/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  

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

@gemini-code-assist
Copy link

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 project's security by upgrading the @storybook/builder-vite dependency. This targeted update resolves two medium-severity Directory Traversal vulnerabilities. It's important to note that the yarn.lock file requires a manual update to fully integrate these changes.

Highlights

  • Dependency Upgrade: Upgraded the @storybook/builder-vite dependency from 0.0.0-use.local (implied by workspace:*) to 0.1.22 in code/frameworks/react-vite/package.json.
  • Security Fix: This upgrade addresses two medium-severity Directory Traversal vulnerabilities, identified as SNYK-JS-TAR-15032660 and SNYK-JS-TAR-15127355, found in the project's yarn dependencies.
  • Automated Remediation: This pull request was automatically generated by Snyk to apply the necessary security fix.
  • Manual Intervention Required: The yarn.lock file failed to update automatically and requires manual intervention to be updated before merging, especially for projects utilizing Yarn's zero-installs 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.

Copy link

@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 @storybook/builder-vite. However, the proposed change incorrectly replaces a yarn workspace dependency (workspace:*) with a fixed, old version (0.1.22). This breaks the monorepo's internal dependency structure and will likely lead to build failures or runtime issues. The correct approach is to address the vulnerability within the local @storybook/builder-vite package, not by pinning to an external, outdated version. I have recommended reverting this change.

"@joshwooding/vite-plugin-react-docgen-typescript": "0.3.1",
"@rollup/pluginutils": "^5.0.2",
"@storybook/builder-vite": "workspace:*",
"@storybook/builder-vite": "0.1.22",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This change replaces the internal workspace dependency (workspace:*) with a specific, old version (0.1.22) from the public registry. This breaks the monorepo's dependency management and is likely to cause issues.

The workspace:* protocol ensures that you are using the version of @storybook/builder-vite that is present in this repository (version 8.3.0-beta.3), not a published one. Pinning to 0.1.22 will pull a very old version and likely break compatibility with other packages in the monorepo.

To fix the underlying security vulnerability, the dependencies of the local @storybook/builder-vite package should be updated, rather than changing how it's referenced here. This change should be reverted.

Suggested change
"@storybook/builder-vite": "0.1.22",
"@storybook/builder-vite": "workspace:*",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants