[Snyk] Fix for 12 vulnerabilities

[hashim21223445]

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

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962463	218
	Infinite loop SNYK-JS-MARKDOWNIT-6483324	160
	Excessive Platform Resource Consumption within a Loop SNYK-JS-BRACES-6838727	159
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	159
	Prototype Pollution SNYK-JS-YARGSPARSER-560381	137
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	131
	Symlink Attack SNYK-JS-TMP-11501554	130
	Prototype Pollution SNYK-JS-UNSETVALUE-2400660	115
	Denial of Service (DoS) npm:mem:20180117	73
	Regular Expression Denial of Service (ReDoS) npm:braces:20180219	58
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	45
	Reverse Tabnabbing SNYK-JS-ISTANBULREPORTS-2328088	35

---

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

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package.json	0% smaller

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, 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 automatically updating several npm development dependencies to resolve a total of 12 identified vulnerabilities. The changes aim to protect the application from various security risks, including critical and high-severity issues, ensuring a more robust and stable codebase.

Highlights

• Vulnerability Resolution: This pull request addresses and fixes 12 identified vulnerabilities within the project's npm dependencies, automatically generated by Snyk.
• Dependency Upgrades: Key development dependencies including 'eslint', 'jsdoc', 'mocha', and 'nyc' have been upgraded to their latest versions to incorporate security fixes.
• Security Impact: The resolved vulnerabilities span various severity levels, including critical and high, mitigating risks such as Incomplete List of Disallowed Inputs, Infinite Loop, Regular Expression Denial of Service (ReDoS), and Prototype Pollution.

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 12 security vulnerabilities by upgrading eslint, jsdoc, mocha, and nyc. While this is beneficial for security, these are all major version upgrades that introduce breaking changes. Most critically, the new versions of these packages require newer Node.js versions than what this project currently supports (>=4.0.0). This will break the build for anyone using an older, but still officially supported, version of Node.js. My review highlights this critical compatibility issue.

[gemini-code-assist]

These dependency upgrades introduce breaking changes due to their Node.js version requirements, which are incompatible with this project's supported Node version (>=4.0.0 as defined in engines).

Specifically:

• eslint@9.0.0 requires Node.js ^18.18.0 || ^20.9.0 || >=22.0.0.
• mocha@11.0.1 requires Node.js ^18.18.0 || ^20.9.0 || >=22.0.0.
• jsdoc@4.0.3 requires Node.js >=16.0.0.
• nyc@15.0.0 requires Node.js >=8.

Merging these changes will cause failures in development and CI environments running on older Node.js versions. To proceed, you'll either need to update the project's supported Node.js version in package.json or find alternative package versions that fix the vulnerabilities while remaining compatible with your supported Node.js range.

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 815c43c.

🟢 All jobs passed!

But CI Insights is watching 👀