Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Breaking] Node v17 crypto removed ripemd160

Open
#29 3 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
cryptography

Research direction

Start with index.js and the related bitcoinjs/bip32 issue to understand how ripemd160 is currently handled and what changed in Node v17. Verify the failure under Node v17, then determine the compatibility behavior required for ripemd160 and confirm it with the project's existing checks.

Written by the indexing model from the issue text.

Description

Related: https://github.com/bitcoinjs/bip32/issues/59

Seems like the only option is:

  1. Check if version >= 17
  2. If true, the index.js should also try to intercept ripemd160 calls and use pure JS.

Thoughts?

Dominant language
JavaScript
Stars
53
Forks
37
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/createHash

All issues in browserify/createHash

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.