[Snyk] Fix for 13 vulnerabilities

[Dustin4444]

Snyk has created this PR to fix 13 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	666
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	666
	Origin Validation Error SNYK-JS-KOACORS-6117545	644
	Arbitrary File Write via Archive Extraction (Zip Slip) SNYK-JS-DECOMPRESSTAR-559095	636
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Cross-site Scripting (XSS) SNYK-JS-SERIALIZEJAVASCRIPT-6147607	626
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MOCHA-2863123	589
	Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905	586
	Improper Input Validation SNYK-JS-NANOID-8492085	529
	Information Exposure SNYK-JS-NANOID-2332193	521
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818	479
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	436

---

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)
🦉 Improper Input Validation
🦉 Cross-site Scripting (XSS)

[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 by resolving 13 identified vulnerabilities across its yarn dependencies. The primary mechanism for this improvement is the upgrade of several development packages, which collectively mitigate various high and medium severity risks, including different forms of Denial of Service, Cross-site Scripting, and other critical security flaws. The changes are confined to package.json, with a crucial note that the yarn.lock file requires manual intervention to be updated correctly.

Highlights

• Automated Vulnerability Fix: This pull request was automatically generated by Snyk to address 13 identified security vulnerabilities within the project's yarn dependencies.
• Dependency Upgrades: Several key development dependencies in package.json have been upgraded to their latest versions to resolve the security issues. These include @vscode/test-web, eslint, glob, mocha, react-testing-library, sinon, terser-webpack-plugin, and vinyl-fs.
• Critical Vulnerabilities Addressed: The fixes target a range of high and medium severity issues, such as Regular Expression Denial of Service (ReDoS), Origin Validation Error, Arbitrary File Write via Archive Extraction (Zip Slip), Missing Release of Resource after Effective Lifetime, Cross-site Scripting (XSS), Improper Input Validation, and Information Exposure.
• Manual yarn.lock Update Required: Snyk was unable to update the yarn.lock file, which requires a manual update by running yarn before merging this pull request.
• Zero-Installs Consideration: For users leveraging Yarn's zero-installs feature, it is necessary to run yarn after pulling these changes to update the .yarn/cache directory, as this PR does not include those updates.

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

[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-99a1703b1a0efeafdf8d3b481bc2b40a

---

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]

Code Review

This pull request, automatically generated by Snyk, addresses 13 security vulnerabilities by upgrading several dependencies. While this is an important security update, it introduces multiple major version upgrades for development dependencies, which will likely cause breaking changes and require significant migration effort.

Most importantly, as noted in the pull request description, the yarn.lock file has not been updated. This is a critical issue that must be resolved by running yarn and committing the updated lock file before merging.

The following packages have received major version upgrades and will likely break your development workflow:

• eslint (7.x to 9.x): This is a major jump. ESLint v9 removed support for the .eslintrc.* configuration files. Your project will need to migrate to the new eslint.config.js format.
• glob (7.x to 9.x): Version 9 is an ESM-only package and can no longer be used with require().
• vinyl-fs (3.x to 4.x): Similar to glob, this is now an ESM-only package and will break scripts that use require().
• mocha (9.x to 11.x), sinon (9.x to 16.x), react-testing-library (7.x to 8.x): These are significant upgrades to your testing libraries. It is highly probable that your test suite will require updates to be compatible with the new APIs.

I've added specific comments on the package.json file highlighting these issues. Please carefully review these breaking changes and plan for the necessary migration work before merging this PR.

[gemini-code-assist]

Upgrading eslint from version 7 to 9 is a major change that includes significant breaking changes. ESLint v9 no longer supports the traditional .eslintrc.* configuration files. Your project uses .eslintrc.json files (e.g., in webpack.config.js), which will cause your linting and build processes to fail.

You will need to migrate your ESLint configuration to the new flat config format (eslint.config.js). You can find the migration guide here: ESLint Migration Guide.

[gemini-code-assist]

The upgrade of glob from version 7 to 9 is a breaking change. glob v9 is an ECMAScript Module (ESM) and can no longer be imported using require().

Your project script at scripts/preprocess-svg.js uses const globCb = require('glob');, which will now fail. You will need to refactor this script to use dynamic import() or convert it to an ES module to use the new version of glob.

[gemini-code-assist]

The upgrade of vinyl-fs from version 3 to 4 is a breaking change. vinyl-fs v4 is an ECMAScript Module (ESM) and can no longer be imported using require().

Your build script at build/hygiene.js uses const vfs = require('vinyl-fs');, which will now fail. This script needs to be updated to handle ESM packages, for example by using dynamic import().

[gemini-code-assist]

This PR includes major version upgrades for several key testing libraries:

• mocha from v9 to v11
• react-testing-library from v7 to v8
• sinon from v9 to v16

These are significant jumps that almost certainly include breaking changes to their APIs. It is very likely that your test suite will fail after these upgrades. You will need to carefully review the changelogs for these packages and update your test files accordingly.