Skip to content

[Snyk] Security upgrade bcrypt from 5.1.0 to 6.0.0#812

Open
adamlaska wants to merge 2 commits into
masterfrom
snyk-fix-ad7b73ea1121cf065426e446a2dcecab
Open

[Snyk] Security upgrade bcrypt from 5.1.0 to 6.0.0#812
adamlaska wants to merge 2 commits into
masterfrom
snyk-fix-ad7b73ea1121cf065426e446a2dcecab

Conversation

@adamlaska

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/bitcore-client/package.json
  • packages/bitcore-client/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Infinite loop
SNYK-JS-TAR-17909068
medium severity Incorrect Type Conversion or Cast
SNYK-JS-TAR-17909104
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-TAR-17909152
medium severity Uncaught Exception
SNYK-JS-TAR-17909225

Breaking Change Risk

Merge Risk: Medium

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
🦉 Uncaught Exception

@adamlaska

Copy link
Copy Markdown
Owner Author

Merge Risk: Medium

This major version upgrade of bcrypt drops support for end-of-life Node.js versions.

Breaking Change:

  • Node.js Support: Support for Node.js versions 16 and older has been removed. Projects running on Node.js v18 or newer are not affected by this change.

Other Changes:

  • The package has switched from node-pre-gyp to prebuildify for managing pre-compiled binaries, which may affect installation in some edge-case environments but is not expected to impact most users.

No changes to the API (e.g., hash, compare) have been documented.

Recommendation:
Verify that your production environment and development machines are running Node.js v18 or a more recent version before upgrading.

Source: CHANGELOG.md

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @adamlaska, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@google-cla

google-cla Bot commented Jul 9, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants