[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• gui/package.json
• gui/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	696
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	623

---

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

[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 project's security posture by upgrading critical JavaScript dependencies. It specifically targets and resolves two identified vulnerabilities: a medium-severity uncontrolled recursion issue and a high-severity resource allocation vulnerability, by updating eslint and next to their latest secure versions.

Highlights

• Dependency Upgrades for Security: The eslint dependency has been upgraded from version 8.40.0 to 9.26.0 to resolve a medium-severity 'Uncontrolled Recursion' vulnerability (SNYK-JS-ESLINT-15102420).
• Dependency Upgrades for Security: The next dependency has been upgraded from version 13.4.2 to 15.5.10 to resolve a high-severity 'Allocation of Resources Without Limits or Throttling' vulnerability (SNYK-JS-NEXT-15104645).

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 from Snyk aims to fix security vulnerabilities by upgrading eslint and next. While addressing security is important, these upgrades introduce critical issues. The eslint upgrade to v9 is incompatible with the existing eslint-config-next version, which will break your linting process. Additionally, next is upgraded to a canary version (15.5.10), which is unstable and not recommended for production. I've provided detailed comments on these issues.

[gemini-code-assist]

Upgrading eslint to v9 is a major breaking change. The eslint-config-next package, which is on version 13.4.2 in your package.json, has a peer dependency on eslint@^8.0.0. This will cause a peer dependency conflict and likely break your linting setup. You should upgrade eslint-config-next to a version compatible with both eslint@9 and next@15.5.10, which would likely be 15.5.10.

[gemini-code-assist]

The next package is being upgraded to version 15.5.10. This appears to be a canary or pre-release version of Next.js. While this upgrade may fix the security vulnerability, using canary releases in a production environment is highly risky as they are not stable and may contain bugs or breaking changes that are not yet documented.

It is recommended to evaluate if a stable version of next (e.g., in the v14 line) also includes the security fix. If not, please be aware of the risks of deploying a canary version to production.