[Snyk] Fix for 2 vulnerabilities

[Dustin4444]

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

Snyk changed the following file(s):

• package.json

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.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	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)
🦉 Prototype Pollution

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

✨ 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-92e69c6125ad2eb7091c7ee6509d59ee

---

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, focuses on enhancing the project's security posture by upgrading two development dependencies, eslint and sinon. These targeted upgrades are designed to resolve specific security vulnerabilities, including Prototype Pollution and Regular Expression Denial of Service, thereby contributing to a more robust and secure codebase.

Highlights

• Automated Security Fix: This pull request was automatically generated by Snyk to address two identified security vulnerabilities within the project's dependencies.
• Dependency Upgrades: The eslint dependency has been upgraded from version "7.22.0" to "9.0.0", and the sinon dependency has been upgraded from "9.0.0" to "21.0.1".
• Vulnerabilities Addressed: These dependency updates aim to remediate a Prototype Pollution vulnerability (SNYK-JS-LODASH-15053838) and a Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-DIFF-14917201).
• Manual yarn.lock Update Required: A warning indicates that the yarn.lock file could not be automatically updated and requires manual intervention to ensure consistency, especially for projects utilizing Yarn's zero-installs feature.

🧠 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 pull request, automatically generated by Snyk, addresses two security vulnerabilities by upgrading eslint and sinon.

Critically, the yarn.lock file has not been updated, as noted in the PR description. You must run yarn install (or equivalent) to generate the updated lockfile and commit it before merging. Without this step, the vulnerabilities will not be fixed, and your CI builds using a frozen lockfile will fail.

Additionally, please be aware that this PR includes major version upgrades for key development dependencies which are marked as breaking changes:

• eslint is upgraded from 7.22.0 to 9.0.0.
• sinon is upgraded from 9.0.0 to 21.0.1.

These are significant jumps that will likely require a migration effort. I've left specific comments on these dependencies with more details. Please ensure you thoroughly test the project to address any breaking changes.

[gemini-code-assist]

Upgrading eslint from version 7 to 9 is a major update that introduces significant breaking changes. For example, ESLint v9 uses a new configuration file format (eslint.config.js) by default and has removed many deprecated rules and APIs. You will likely need to update your ESLint configuration and potentially fix new linting errors. Please consult the ESLint v8 migration guide and ESLint v9 migration guide for details.

[gemini-code-assist]

This is a very large major version jump for sinon, from version 9 to 21. This upgrade will almost certainly introduce breaking changes to your tests. There have been many API changes between these versions. You should carefully review the sinon changelogs and update your tests accordingly. Thoroughly run your test suite to catch any regressions.