[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/sveltekit/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, automatically generated by Snyk, aims to enhance the security posture of the project by resolving identified vulnerabilities within the sveltekit framework's dependencies. It specifically targets and mitigates two security risks by upgrading several Storybook-related packages to their patched versions, ensuring a more secure and stable development environment.

Highlights

• Security Vulnerability Fixes: This pull request addresses two critical 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 Upgrades: Upgraded @storybook/builder-vite to 0.1.22, @storybook/svelte to 4.0.0, and @storybook/svelte-vite to 9.0.0 in code/frameworks/sveltekit/package.json to mitigate the identified vulnerabilities.

Changelog

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

Activity

• This pull request was automatically generated by Snyk to fix identified vulnerabilities.
• A warning was issued indicating that the yarn.lock file failed to update and requires manual resolution.
• The PR description provides links to Snyk reports and interactive lessons for the vulnerabilities.

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 are incorrect for this monorepo structure. It replaces workspace:* references with pinned versions from npm, which will likely break the build and the @storybook/sveltekit package by using incompatible and outdated/future versions of internal packages. This change should be rejected. The vulnerabilities need to be addressed differently, for example by updating the transitive dependencies within the workspace packages or using yarn's resolutions feature. Additionally, as noted in the PR description, the yarn.lock file was not updated, which would require manual intervention even if the dependency changes were correct.

[gemini-code-assist]

These changes from workspace:* to pinned versions are incorrect for this monorepo setup. Using workspace:* ensures that local packages from this monorepo are used, which is the intended behavior. Pinning to external npm versions, especially with such drastic version changes (e.g., @storybook/builder-vite from a workspace version of 8.3.0-beta.3 to 0.1.22), will likely break the build and the functionality of the @storybook/sveltekit package. The vulnerabilities should be addressed by updating the dependencies within the workspace packages themselves or by using resolutions in the root package.json if applicable, not by breaking the workspace linking.

Suggested change

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