[Snyk] Security upgrade bcrypt from 1.0.0 to 5.0.1

[saurabharch]

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

Snyk changed the following file(s):

• final/gateway/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	713

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the project by resolving a critical vulnerability. It achieves this by updating a key dependency to a more secure version, thereby mitigating potential risks associated with the identified weakness.

Highlights

• Security Vulnerability Fix: This pull request addresses and fixes one security vulnerability, "Improper Handling of Unicode Encoding" (SNYK-JS-TAR-15038581), identified by Snyk with a score of 713.
• Dependency Upgrade: The fix is implemented by upgrading the bcrypt dependency from version 1.0.0 to 5.0.1 in final/gateway/package.json.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades bcrypt from version 1.0.0 to 5.0.1 to fix a security vulnerability. However, this upgrade introduces two critical breaking changes that will prevent the application from building and running correctly.

1. Node.js Version Incompatibility: bcrypt@5.0.1 requires Node.js version 10 or higher. This project is configured to use Node.js 6+ ("engines": { "node": ">= 6.0.0" } in package.json) and the Dockerfile is based on node:8-alpine. The npm install command will fail due to this version mismatch.

2. API Breaking Changes: bcrypt version 5.0.0 and later removed callback support for its asynchronous functions, which now exclusively return Promises. The codebase likely relies on the old callback-based API (or a promisification wrapper), which will cause runtime errors in features like user authentication.

To resolve this, you must:

• Update the Node.js version in your Dockerfile and CI/CD environment to a compatible version (>=10).
• Update the engines field in package.json.
• Refactor the code that uses bcrypt (e.g., in lib/services/utils.js) to use the new Promise-based API.

Merging this PR as-is will break the build.

[gemini-code-assist]

This upgrade to bcrypt@5.0.1 introduces two critical breaking changes:

1. Node.js Version Requirement: bcrypt@5.0.1 requires Node.js >= 10. Your Dockerfile uses node:8-alpine, and your package.json specifies node >= 6.0.0. This will cause npm install to fail. You need to upgrade your Node.js environment.

2. API Changes: Asynchronous functions in bcrypt (like compare and hash) now only return Promises and no longer support callbacks. Any code using the old API will break. For example, utils.compareSaltAndHashed (used in lib/services/auth.js) will need to be updated to work with the new Promise-based API.

This PR cannot be merged without addressing these issues by updating the Node.js environment and refactoring the code that uses bcrypt.