[Snyk] Security upgrade bcrypt from 5.0.1 to 6.0.0

[BryanFRD]

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
	Directory Traversal SNYK-JS-TAR-15032660	693

---

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:

🦉 Directory Traversal

[Copilot]

Pull request overview

Updates the bcrypt dependency to address a reported npm vulnerability (via Snyk), with corresponding lockfile changes.

Changes:

• Bump bcrypt from ^5.0.1 to ^6.0.0 in package.json.
• Regenerate package-lock.json to reflect bcrypt@6 and its new dependency tree (notably removing @mapbox/node-pre-gyp/tar chain).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates the direct dependency version for bcrypt to ^6.0.0.
package-lock.json	Updates resolved package graph for bcrypt@6, including its Node engine requirement and dependency changes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading to bcrypt@6 introduces a Node.js engine requirement (>=18 per the lockfile). To avoid surprise install/runtime failures in environments still on Node 16/14, declare an explicit "engines.node" constraint (and/or document/ensure CI+deployment use Node 18+) as part of this upgrade, or choose an alternative remediation that keeps Node compatibility.