[Snyk] Fix for 4 vulnerabilities

[St0nersdash]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Excessive Platform Resource Consumption within a Loop SNYK-JS-BRACES-6838727	696
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	589
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	508

---

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)

[gemini-code-assist]

Summary of Changes

Hello @St0nersdash, 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 was automatically generated by Snyk to fix known security vulnerabilities in the project's npm dependencies by updating package versions. The changes are limited to the package manifest and lock files.

Highlights

• Security Vulnerabilities: This PR addresses 4 security vulnerabilities identified by Snyk in the project's npm dependencies. These include high, medium, and low severity issues related to resource consumption, resource release, and regular expression complexity/ReDoS.
• Dependency Updates: The primary change involves updating specific dependencies to versions that contain fixes for the reported vulnerabilities.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​29.6.0 ⏵ 30.0.0	+1		+1	+1
	semver@​7.7.1 ⏵ 7.7.2	+1		+1
	jest-circus@​29.7.0 ⏵ 30.0.0	+1		+1

View full report

[gemini-code-assist]

Code Review

This Snyk PR upgrades jest and jest-circus from ^29.x and ^27.x respectively to ^30.0.0 to address 4 security vulnerabilities. This is a positive security enhancement.

However, these are major version upgrades, and Snyk's metadata indicates isBreakingChange:true. The most significant concern identified is the potential incompatibility of the new Jest versions with other development dependencies in your project, specifically:

• ts-jest (currently ^27.0.5)
• @types/jest (currently ^27.0.2)

These packages will likely need to be upgraded to versions compatible with Jest 30 to ensure your test suite remains functional and type-correct. Please verify compatibility (including with your TypeScript version ^3.8.3 for ts-jest) and update them as necessary.

Thorough testing of your application and test suite is crucial after applying these changes and any related dependency updates. Reviewing the Jest 30 migration guide is also highly recommended.

[gemini-code-assist]

Upgrading jest and jest-circus to a new major version (^30.0.0) is a good step for addressing the listed vulnerabilities.
However, major version upgrades can introduce breaking changes, and Snyk has indeed flagged this PR with isBreakingChange:true in its metadata.

Key concerns regarding compatibility with other development dependencies in your package.json:

• ts-jest: Currently at ^27.0.5. Jest 30 likely requires a newer version of ts-jest. Using an incompatible version can lead to test failures, incorrect test behavior, or build issues.
• @types/jest: Currently at ^27.0.2. These type definitions are for Jest 27 and may not be accurate for Jest 30, potentially leading to type errors during development or incorrect autocompletion.

Please take the following steps:

1. Consult the ts-jest documentation (usually on their GitHub page or official website) to find the version compatible with Jest 30. Update ts-jest in package.json accordingly. Also, verify its compatibility with your current TypeScript version (^3.8.3), as newer ts-jest versions might require a more recent TypeScript.
2. Update @types/jest to a version compatible with Jest 30.
3. After these upgrades, run all tests thoroughly (unit, integration, etc.) to ensure everything works as expected.
4. It's also advisable to review the Jest 30 migration guide for any other potential breaking changes, new configurations, or best practices that might affect your project.