[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):

• gui/package.json
• gui/yarn.lock

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.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	147
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	61

---

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, focuses on enhancing the security posture of the project by upgrading key JavaScript dependencies. The primary goal is to resolve identified vulnerabilities, ensuring the application remains robust against known threats. The changes involve updating the package.json and yarn.lock files to reflect these necessary dependency bumps.

Highlights

• Vulnerability Fixes: This pull request addresses two security vulnerabilities identified by Snyk: a high-severity 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-NEXT-15104645) and a medium-severity 'Regular Expression Denial of Service (ReDoS)' (SNYK-JS-DIFF-14917201).
• Dependency Upgrades: To mitigate these vulnerabilities, the diff2html package has been upgraded from version 3.4.48 to 3.4.56, and the next framework has been updated from 14.2.2 to 15.5.10.
• Yarn Zero-Installs Note: For projects utilizing Yarn's zero-installs feature, it's important to note that this PR does not update the .yarn/cache/ directory. Developers will need to run yarn locally to ensure the cache is updated and the project can be developed on immediately.

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, addresses two security vulnerabilities by upgrading next and diff2html dependencies.

My main concern is the upgrade of next from version 14 to a canary release of version 15 (15.5.10). This is a major version bump to an unstable release, which carries a high risk of introducing breaking changes and other bugs. This should be carefully evaluated and tested.

Additionally, the update to diff2html brings in major version changes for its transitive dependencies, which could also lead to unexpected issues.

I've added specific comments on package.json with more details. Thorough testing of the application is crucial before merging this PR.

[gemini-code-assist]

This pull request upgrades next from version 14.2.2 to 15.5.10. This is a major version upgrade to a canary (unstable) release of Next.js. Using canary releases in a production environment is highly risky as they are not considered stable and may contain bugs or breaking changes that are not yet documented. While this upgrade is intended to fix a security vulnerability, the team should carefully evaluate the risks of using an unstable version against the severity of the vulnerability. It is strongly recommended to perform thorough testing across the entire application. Consider waiting for a stable Next.js release that includes this security fix, or exploring alternative mitigations for the vulnerability.

[gemini-code-assist]

While diff2html is only a patch update, it introduces major version changes for its dependencies. Specifically, diff is upgraded from 5.1.0 to 8.0.3, and hogan.js is replaced by @profoundlogic/hogan. These are significant changes that could introduce breaking changes in how diff2html parses diffs. Since you are using diff2html's parse function in MonacoDiffEditor.tsx, please ensure this functionality is thoroughly tested to prevent any regressions.