[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-15127355	596

---

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

Upgrades bcrypt to address a Snyk-reported directory traversal vulnerability (via removal of vulnerable transitive tar usage).

Changes:

• Bump bcrypt from ^5.0.1 to ^6.0.0 in package.json.
• Regenerate package-lock.json to reflect the new bcrypt version and updated transitive dependency graph (notably replacing node-pre-gyp/tar chain with node-gyp-build).

Reviewed changes

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

File	Description
package.json	Updates direct dependency bcrypt to ^6.0.0 for vulnerability remediation.
package-lock.json	Updates the resolved dependency tree for bcrypt@6.0.0, removing prior transitive packages and recording new engine/dependency constraints.

---

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

[Copilot]

bcrypt 6.x requires Node.js >= 18 (see its engines field in the lockfile). Since this is a breaking runtime/install requirement and package.json currently doesn’t declare an engine constraint, consider adding an explicit "engines": {"node": ">=18"} (and aligning CI/deployment) or pinning bcrypt to a compatible major if you must support older Node versions.