[Snyk] Fix for 5 vulnerabilities

[niravparikh05]

Snyk has created this PR to fix 5 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
	Infinite loop SNYK-JS-TAR-17909068	828
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152	828
	Incorrect Type Conversion or Cast SNYK-JS-TAR-17909104	738
	Uncaught Exception SNYK-JS-TAR-17909225	738
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncaught Exception

[niravparikh05]

This release includes major version upgrades for Jest, tar, and bcrypt, introducing significant breaking changes that require developer attention.

Top 3 Most Impactful Upgrades:

• jest-cli, jest-jasmine2, jest-runner, jest-runtime (26.6.3 → 27.0.0): HIGH RISK

  • Jest v27 introduces stricter test validation that will cause tests to fail if not addressed. Key changes include disallowing the done callback from being called more than once, and prohibiting the combination of calling done and returning a Promise in the same test.
  • Several long-deprecated functions have been removed, such as jest.addMatchers, jest.resetModuleRegistry, and jest.runTimersToTime.
  • The default test environment has changed, which may affect projects that rely on a DOM environment.
  • Recommendation: Developers must review asynchronous tests to ensure they comply with the new, stricter callback and Promise handling rules. Replace any usage of removed deprecated functions with their modern equivalents (e.g., expect.extend).

• tar (6.2.1 → 7.5.19): MEDIUM RISK

  • This major version upgrade drops support for Node.js versions below 18.
  • The library has been rewritten in TypeScript, providing both ESM and CommonJS interfaces.
  • The default behavior of the chmod option has been reversed, which could affect file permissions during extraction.
  • Recommendation: Verify that your production environment runs on Node.js 18 or newer. Review any scripts using the tar library to ensure the new chmod default does not adversely affect file permissions.

• bcrypt (5.1.1 → 6.0.0): MEDIUM RISK

  • This major version upgrade drops support for Node.js versions 16 and below.
  • The build system was changed from node-pre-gyp to prebuildify, which should not impact most users but is a notable internal change.
  • Recommendation: Ensure your deployment environment uses a supported version of Node.js (v18+ is recommended, aligning with the tar upgrade).

These upgrades introduce necessary but potentially breaking changes, primarily related to Node.js version support and stricter test enforcement. Careful review and testing are required before merging.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.