[Snyk] Security upgrade bcrypt from 5.1.1 to 6.0.0

[qbey]

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

Snyk changed the following file(s):

• server/package.json
• server/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Infinite loop SNYK-JS-TAR-17909068	710
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152	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

[qbey]

This major version upgrade of bcrypt introduces a significant change to the supported Node.js environment.

Breaking Change:

• Node.js Support: Support for Node.js versions 16 and older has been dropped. Node.js 18 or newer is now required. Node.js 16 reached its end-of-life in September 2023.

There are no documented changes to the package's API, so no code modifications should be necessary if your environment meets the new requirement. The change primarily affects the build system by replacing node-pre-gyp with prebuildify.

Recommendation:
Verify that your deployment environment is running Node.js version 18 or higher before upgrading.

Source: Changelog

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 54a19e00-d81c-4aef-a356-ac3d3fdc3fa9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}