[Snyk] Fix for 2 vulnerabilities

[earthiverse]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

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 @earthiverse, 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 project's security posture by resolving two identified vulnerabilities. It achieves this by upgrading key npm dependencies, specifically express and eslint, to versions that incorporate the necessary security patches and improve overall stability.

Highlights

• Vulnerability Fixes: Addressed two 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 the express dependency from 4.17.3 to 4.22.0 and the eslint dev dependency from 8.11.0 to 10.0.0 to resolve the identified security issues.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• package-lock.json
  • Updated locked versions for express, eslint, and their transitive dependencies to reflect the changes in package.json.
• package.json
  • Upgraded express dependency from ^4.17.3 to ^4.22.0.
  • Upgraded eslint dev dependency from ^8.11.0 to ^10.0.0.

Activity

• Snyk automatically created this pull request to fix 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, automatically generated by Snyk, aims to fix two security vulnerabilities by upgrading express and eslint.

The upgrade of express from ^4.17.3 to ^4.22.0 is a minor version bump and appears safe, addressing one of the vulnerabilities.

However, the upgrade of eslint from ^8.11.0 to ^10.0.0 is a major version jump. Snyk's own metadata flags this as a breaking change ("isBreakingChange":true). My review confirms this will break your development setup. The project's ESLint plugins, @typescript-eslint/parser and @typescript-eslint/eslint-plugin, are at version ^5.16.0, which is not compatible with eslint@10. This will cause peer dependency errors during installation and break your linting commands.

I've added a critical comment with details on how to resolve this by upgrading the related @typescript-eslint packages.

[gemini-code-assist]

The upgrade of eslint to v10 is a major version bump that introduces breaking changes. The versions of @typescript-eslint/parser (^5.16.0) and @typescript-eslint/eslint-plugin (^5.16.0) used in this project are not compatible with eslint@10. Their peer dependencies require eslint version ^6.0.0 || ^7.0.0 || ^8.0.0.

This incompatibility will cause npm install to report peer dependency conflicts and will likely break your linting setup.

To fix this, you need to also upgrade @typescript-eslint/parser and @typescript-eslint/eslint-plugin to a version that is compatible with eslint@10. Based on the @typescript-eslint release notes, you should upgrade them to ^8.0.0 or a newer version.