[Snyk] Fix for 3 vulnerabilities

[q1blue]

Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• scripts/package.json
• scripts/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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	102
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	62

---

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 addresses three critical security vulnerabilities, including two Regular Expression Denial of Service (ReDoS) issues and one resource allocation vulnerability, by upgrading several key dependencies. The changes primarily involve updating eslint, express, and prettier-plugin-merge to their latest secure versions, thereby enhancing the project's overall security posture and mitigating potential risks.

Highlights

• Security Vulnerabilities Fixed: Resolved three security vulnerabilities identified by Snyk, including two Regular Expression Denial of Service (ReDoS) issues and one resource allocation vulnerability.
• Dependency Upgrades: Upgraded eslint from ^8.57.0 to ^10.0.0, express from ^4.19.2 to ^4.22.0, and prettier-plugin-merge from ^0.7.0 to ^0.9.1.
• Affected Files: Updated scripts/package.json and scripts/yarn.lock to reflect the dependency upgrades.

Changelog

• scripts/package.json
  • Updated eslint dependency from ^8.57.0 to ^10.0.0.
  • Updated express dependency from ^4.19.2 to ^4.22.0.
  • Updated prettier-plugin-merge dependency from ^0.7.0 to ^0.9.1.
• scripts/yarn.lock
  • Updated to reflect the new dependency versions specified in package.json.

Activity

• Automatically generated by Snyk to propose fixes for identified security vulnerabilities.
• Includes detailed information about the vulnerabilities being addressed and guidance for users leveraging Yarn's zero-installs feature.

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 Snyk PR updates dependencies to fix three vulnerabilities. While the minor bumps for express and prettier-plugin-merge are fine, the major upgrade of eslint from v8 to v10 is highly risky. It's likely to break your linting setup due to significant breaking changes in ESLint. I've added a critical comment suggesting a safer alternative: using a yarn resolution to patch the vulnerable ajv package directly, without the disruptive eslint upgrade.

[gemini-code-assist]

This upgrade of eslint from v8 to v10 is a major version bump that will likely break your linting setup. ESLint v9 introduced a new configuration system (flat config), and many plugins require updates for compatibility with v9/v10. Your project's .eslintrc.cjs is using the legacy format.

The vulnerability this change aims to fix is in ajv, a transitive dependency. A safer alternative is to force a specific version of ajv using a resolutions field in package.json. This avoids the breaking changes from a major eslint upgrade.

I recommend reverting this change and adding the following to your resolutions in package.json:

"resolutions": {
  ...
  "ajv": ">=6.12.6"
}

Then run yarn install to apply the resolution.

Suggested change

	"eslint": "^10.0.0",
	"eslint": "^8.57.0",