Skip to content

Conversation

@q1blue
Copy link

@q1blue q1blue commented Feb 2, 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-webpack5/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 automates a critical security update for the @storybook/builder-webpack5 dependency. Its primary purpose is to mitigate two medium-severity directory traversal vulnerabilities, ensuring the project's security posture is maintained by upgrading the package to a patched version. The change is confined to a single package.json file.

Highlights

  • Dependency Upgrade: Upgraded the @storybook/builder-webpack5 dependency from 0.0.0-use.local to 7.1.0 in code/frameworks/react-webpack5/package.json.
  • Security Fix: This upgrade addresses two medium-severity Directory Traversal vulnerabilities (SNYK-JS-TAR-15032660 and SNYK-JS-TAR-15127355) identified by Snyk.
  • Automated Pull Request: This pull request was automatically generated by Snyk to apply the necessary security updates.
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-webpack5. However, the proposed change incorrectly replaces the workspace:* dependency with a pinned, older version (7.1.0). This is a downgrade from the current monorepo version (8.3.0-beta.3) and will likely break the monorepo's internal dependency structure, causing build failures or runtime issues. The warning in the PR description about yarn.lock failing to update further indicates that this change is problematic. It is recommended to reject this change and address the underlying vulnerability within the @storybook/builder-webpack5 package directly.

},
"dependencies": {
"@storybook/builder-webpack5": "workspace:*",
"@storybook/builder-webpack5": "7.1.0",

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 workspace:* protocol with a pinned version 7.1.0. This is problematic for several reasons:

  1. Downgrade: The version of @storybook/builder-webpack5 in this monorepo is 8.3.0-beta.3. Pinning to 7.1.0 is a significant downgrade and will likely introduce breaking changes or inconsistencies, as other @storybook packages are on version 8.3.0-beta.3.
  2. Monorepo Integrity: Using workspace:* ensures that local packages within the monorepo are used. Hardcoding a version bypasses this, pulling an older version from the npm registry instead of using the code from code/builders/builder-webpack5.

This automated change by Snyk seems to misunderstand the monorepo setup. While the intent is to fix a vulnerability, this approach is incorrect and will likely break the build. The vulnerability should be addressed within the @storybook/builder-webpack5 package itself, or by upgrading the entire monorepo if a fix is available in a newer version.

    "@storybook/builder-webpack5": "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