[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
	Prototype Pollution SNYK-JS-AXIOS-15252993	225
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157

---

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)
🦉 Prototype Pollution

[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 resolving two high-severity vulnerabilities found in its npm dependencies. It updates key packages to their patched versions, mitigating risks associated with Prototype Pollution and Regular Expression Denial of Service.

Highlights

• Dependency Upgrade: axios: Upgraded the axios dependency from ^1.4.0 to ^1.13.5 to mitigate a high-severity Prototype Pollution vulnerability (SNYK-JS-AXIOS-15252993).
• Dependency Upgrade: eslint: Upgraded the eslint dependency from 8.40.0 to 10.0.0 to address a high-severity Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-AJV-15274295), likely resolved through an indirect dependency update.

Changelog

• gui/package.json
  • Updated axios dependency version.
  • Updated eslint dependency version.

Activity

• This pull request was automatically created by Snyk to propose fixes for identified 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 from Snyk aims to fix two security vulnerabilities by upgrading axios and eslint. The axios upgrade appears to be safe. However, the upgrade of eslint from version 8 to 10 is a significant breaking change. It conflicts with the peer dependency requirements of eslint-config-next and is very likely to break your build process. I have left a critical comment on gui/package.json suggesting an alternative, safer approach using npm overrides to patch the vulnerability without the major version bump.

[gemini-code-assist]

This upgrade of eslint from version 8 to 10 is a major breaking change. The eslint-config-next package (version 13.4.2) in your dependencies requires eslint@^7.23.0 || ^8.0.0. This mismatch will cause a peer dependency conflict and likely break your CI/CD pipeline.

The vulnerability this upgrade is trying to fix is in ajv, a transitive dependency. A much safer approach is to use an overrides block in package.json to force ajv to a non-vulnerable version, without the need for a major eslint upgrade.

For example, you can add this to your package.json:

"overrides": {
  "ajv": "^6.12.6"
}

This will resolve the security vulnerability without introducing breaking changes.

Suggested change

	"eslint": "10.0.0",
	"eslint": "8.40.0",