[Snyk] Fix for 4 vulnerabilities

[q1blue]

Snyk has created this PR to fix 4 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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	208
	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-JS-TAR-6476909	133
	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

[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 significantly enhances the project's security posture by upgrading critical dependencies to versions that contain fixes for known vulnerabilities. The primary goal is to mitigate risks associated with issues like Prototype Pollution and Regular Expression Denial of Service, ensuring a more secure and stable application environment.

Highlights

• Dependency Upgrades: Several key dependencies have been upgraded to their latest versions, including lodash from ^4.17.21 to ^4.17.23, node-gyp from ^9.3.1 to ^11.0.0, remark from ^14.0.3 to ^15.0.0, remark-lint from ^9.1.2 to ^10.0.0, and remark-preset-lint-recommended from ^6.1.3 to ^7.0.0.
• Vulnerability Resolution: This pull request addresses four medium-severity security vulnerabilities identified by Snyk, including issues related to Improper Handling of Unicode Encoding, Uncontrolled Resource Consumption (both affecting tar), Prototype Pollution (lodash), and Regular Expression Denial of Service (diff).

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 four security vulnerabilities by upgrading several dependencies. The changes include updates to lodash, node-gyp, and remark-related packages. While these upgrades are essential for security, please note that several are major version bumps (node-gyp v9 to v11, remark v14 to v15, etc.), which carry a risk of introducing breaking changes. I've added specific comments highlighting these major upgrades. It's crucial that the project's test suite is run to ensure these changes do not introduce any regressions.

[gemini-code-assist]

Upgrading node-gyp from v9 to v11 is a major version change. This could introduce breaking changes. While this upgrade is necessary to fix security vulnerabilities, it's important to be aware of the potential impact on the build process.

[gemini-code-assist]

This PR includes major version upgrades for remark and its related linting packages (remark v14 -> v15, remark-lint v9 -> v10, remark-preset-lint-recommended v6 -> v7). These major upgrades could introduce breaking changes to the markdown processing and linting setup. It's important to be aware of the potential impact on documentation generation and linting.