[Snyk] Fix for 1 vulnerabilities

[TheRedHatter]

Snyk has created this PR to fix 1 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
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18512280	710

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

[TheRedHatter]

This upgrade includes a major and high-risk update to rimraf, and a medium-risk update to bcrypt.

Top 3 Most Impactful Changes

1. rimraf (3.0.2 → 6.1.1) - HIGH RISK

This is a significant multi-version jump with several major breaking changes. Code modifications are required.

• v3 → v4: The primary API is now Promise-based instead of using callbacks. Code using callbacks must be refactored to use Promises.
• Globbing: Automatic glob pattern support was removed in v4 and now requires an explicit { glob: true } option or --glob CLI flag.
• v4 → v5: The default export was removed. You must switch to named imports (e.g., import { rimraf } from 'rimraf').
• Node.js Support: Support for older Node.js versions has been dropped. v4 requires Node.js >= 14, and v6 requires Node.js >= 20.

Recommendation: Due to the extensive breaking changes, this upgrade should be handled carefully. Review all usages of rimraf to update from callbacks to Promises, switch to named imports, and explicitly enable glob support where needed.

2. bcrypt (5.0.1 → 6.0.0) - MEDIUM RISK

This major version upgrade introduces a breaking change related to the runtime environment.

• Node.js Support: Support for Node.js versions 16 and older has been dropped.

Recommendation: Ensure your production environment and development workflows are running on a Node.js version greater than 16 before merging this upgrade.

3. libxmljs (0.19.7 → 0.19.8) - LOW RISK

This is a patch release. No breaking changes are documented or expected.

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

[TheRedHatter]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

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

[TheRedHatter]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	libxmljs@​0.19.7 ⏵ 0.19.8	+1		+1		+11
	rimraf@​6.1.1
	bcrypt@​5.0.1 ⏵ 6.0.0	+9

View full report