[Snyk] Fix for 4 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• code/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
	Directory Traversal SNYK-JS-TAR-15032660	149
	Directory Traversal SNYK-JS-TAR-15127355	129
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	112
	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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Directory Traversal

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! 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 posture by upgrading several core dependencies. The updates resolve four distinct vulnerabilities, ranging from directory traversal to resource allocation issues. Reviewers should note the critical requirement to manually update the yarn.lock file after these changes are applied.

Highlights

• Dependency Upgrades for Security: This PR upgrades several key dependencies, including @nx/eslint, @storybook/angular, @storybook/nextjs, and eslint, to address a total of four identified security vulnerabilities.
• Vulnerabilities Addressed: The upgrades specifically target two medium-severity Directory Traversal issues (SNYK-JS-TAR), one high-severity Allocation of Resources Without Limits or Throttling issue (SNYK-JS-NEXT), and one medium-severity Uncontrolled Recursion issue (SNYK-JS-ESLINT).
• Manual yarn.lock Update Required: Due to an automated failure, the yarn.lock file was not updated by Snyk. A manual 'yarn' command execution is required to update yarn.lock and the .yarn/cache directory (for zero-install users) before merging.

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. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix four vulnerabilities by upgrading several dependencies. While the intent is good, there are critical issues that need to be addressed before merging.

Most importantly, as noted in the PR description, the yarn.lock file has not been updated. This is a required step to ensure the dependency changes are correctly applied and must be done before merging.

Additionally, this PR introduces significant and likely breaking downgrades for @storybook/angular and @storybook/nextjs, changing them from workspace-linked versions to much older, fixed versions. These changes are highly suspect, likely to break the project, and should be reverted in favor of a more targeted fix, such as using yarn's resolutions feature.

Finally, the upgrade of eslint to a new major version (v9) will likely require configuration changes. Please review the ESLint migration guide to ensure a smooth transition.

[gemini-code-assist]

This change downgrades @storybook/angular from a workspace-linked version (which resolves to ~8.3.0-beta.3) to a much older version 3.3.0. This is a significant downgrade that will almost certainly introduce breaking changes and is likely an incorrect resolution by Snyk for vulnerabilities in transitive dependencies like tar.

Instead of downgrading this package, the underlying vulnerability should be addressed directly, for instance by adding a resolution for the vulnerable package in package.json. For example, to fix the tar vulnerabilities, you could add:

"resolutions": {
  "tar": ">=6.2.1"
}

I recommend reverting this change and applying a more targeted fix.

[gemini-code-assist]

Similar to the change for @storybook/angular, this downgrades @storybook/nextjs from a workspace-linked version (~8.3.0-beta.3) to 7.0.0. This is a major downgrade and is likely to cause breakages. This seems to be an incorrect fix from Snyk, probably to address a vulnerability in a transitive dependency.

A better approach would be to add a resolution for the vulnerable package in package.json rather than downgrading @storybook/nextjs. For example, if the vulnerability is in tar, you could add a resolution for it.

I recommend reverting this change and applying a more targeted fix.