[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• code/frameworks/svelte-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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	803
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	708

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling

[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 automates the resolution of critical security vulnerabilities within the project's dependencies. By updating specific package versions, it mitigates known risks associated with Regular Expression Denial of Service and resource allocation without limits, enhancing the overall security posture of the application.

Highlights

• Vulnerability Fix: This PR, automatically generated by Snyk, addresses two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
• Dependency Updates: The fix involves updating @storybook/builder-vite from workspace:* to 0.1.22 and @storybook/svelte from workspace:* to 4.0.0 in code/frameworks/svelte-vite/package.json.

Changelog

• code/frameworks/svelte-vite/package.json
  • Updated @storybook/builder-vite dependency from workspace:* to 0.1.22.
  • Updated @storybook/svelte dependency from workspace:* to 4.0.0.

Activity

• This pull request was automatically created by Snyk to fix identified vulnerabilities.
• A warning was noted that yarn.lock failed to update and requires manual intervention.
• The PR suggests running yarn to update the .yarn/cache/ directory for zero-install users.

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 two security vulnerabilities by updating dependencies. However, the proposed changes in code/frameworks/svelte-vite/package.json are incorrect. It replaces workspace:* dependencies with old, fixed versions, which is a significant downgrade that will likely break the project's build and functionality within the monorepo structure. The correct approach would be to address the vulnerabilities in the source packages (@storybook/builder-vite and @storybook/svelte) rather than downgrading them here. I've added a comment to revert these changes.

[gemini-code-assist]

This change replaces workspace:* with fixed, old versions for @storybook/builder-vite and @storybook/svelte. This is a significant downgrade that will likely break the project. In a monorepo, workspace:* ensures that this package uses the current code from other local packages. Pinning to old, published versions (0.1.22 and 4.0.0) instead of the current workspace version (8.3.0-beta.3) is incorrect. The underlying vulnerabilities should be addressed in the respective workspace packages, not by downgrading them here.

    "@storybook/builder-vite": "workspace:*",
    "@storybook/svelte": "workspace:*"