[Snyk] Fix for 2 vulnerabilities

[Dustin4444]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	61
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	60

---

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)

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-41cbd5f1551c35cf0e2e10058d6ca8ea

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, 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 upgrading key development dependencies. The changes specifically target and resolve two identified vulnerabilities, ensuring a more robust and secure development environment.

Highlights

• Dependency Upgrades: The eslint dependency has been updated from version ^8.39.0 to ^9.26.0, and the mocha dependency has been upgraded from ^10.2.0 to ^10.6.0.
• Vulnerability Resolution: These dependency updates address two identified security vulnerabilities: a Regular Expression Denial of Service (ReDoS) (SNYK-JS-DIFF-14917201) and an Uncontrolled Recursion vulnerability (SNYK-JS-ESLINT-15102420).
• Manual Intervention Required: The package-lock.json file was not automatically updated by Snyk and requires manual updating before this pull request can be merged.

🧠 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.

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 pull request upgrades eslint and mocha to fix two security vulnerabilities. While the dependency upgrades are correct for fixing the vulnerabilities, there are critical actions you need to take before merging. The eslint upgrade is a major version bump from v8 to v9, which includes breaking changes and requires a manual migration of your configuration file. Furthermore, the package-lock.json file was not updated and needs to be regenerated by running npm install. I've added a comment with more details and a link to the ESLint migration guide.

[gemini-code-assist]

This major version upgrade for ESLint (v8 to v9) introduces significant breaking changes that require manual intervention. Before merging, please address the following:

1. ESLint Configuration Migration: ESLint v9 uses a new configuration file format (eslint.config.js) by default and has removed many deprecated rules and APIs. Your project's current ESLint setup will likely break. Please follow the ESLint v9 migration guide to update your configuration.

2. Update Lockfile: As noted in the PR description, package-lock.json is out of sync. You need to run npm install and commit the updated package-lock.json file.

Given the breaking changes, this automated upgrade requires careful manual review and updates to ensure your project's tooling continues to work correctly.