[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
	Command Injection SNYK-JS-GLOB-14040952	240
	Prototype Pollution SNYK-JS-JSYAML-13961110	49

---

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:

🦉 Command Injection
🦉 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-e92831189f8c75bc16e2d1d4ed999dc8

---

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 aims to enhance the project's security posture by automatically updating vulnerable npm dependencies. It addresses specific Command Injection and Prototype Pollution vulnerabilities through targeted package upgrades. While the package.json has been updated, a manual step is required to synchronize the package-lock.json file, ensuring all dependency changes are correctly reflected and locked.

Highlights

• Security Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses two critical security vulnerabilities: a high-severity Command Injection (SNYK-JS-GLOB-14040952) and a medium-severity Prototype Pollution (SNYK-JS-JSYAML-13961110).
• Dependency Upgrades: To mitigate the identified vulnerabilities, the glob dependency has been upgraded from version 11.0.0 to 11.1.0, and js-yaml has been updated from 4.1.0 to 4.1.1. Additionally, eslint has been upgraded from 8.57.1 to 9.0.0.
• Manual Intervention Required: A warning indicates that the package-lock.json file failed to update automatically and requires manual intervention before merging to ensure dependency consistency.

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 from Snyk addresses two security vulnerabilities by updating glob and js-yaml. It also includes a major version upgrade for eslint from v8 to v9. This is a significant update with breaking changes, particularly regarding the configuration file format, which I've detailed in a specific comment. As noted in the pull request description, package-lock.json has not been updated. Please remember to run npm install to regenerate the lockfile and commit the changes before merging.

[gemini-code-assist]

This pull request upgrades ESLint from v8 to v9. This is a major version upgrade that introduces significant breaking changes. Most notably, ESLint v9 uses a new configuration file format (eslint.config.js) by default and deprecates the eslintrc format used in this project (via eslintConfig in package.json).

Before merging, please ensure that the ESLint setup is migrated to be compatible with v9 and that all linting checks pass. You can find detailed instructions in the official ESLint migration guide.