Ideas for next major update

paulmillr / noble-hashes

Audited & minimal JS implementation of hash functions, MACs and KDFs.

https://paulmillr.com/noble

MIT License

524 stars 39 forks source link

Ideas for next major update #88

Open paulmillr opened 2 months ago

paulmillr commented 2 months ago

Remove cryptoNode import! Requires to ditch support for nodejs v18 (EOL 30 Apr 2025)
Remove import maps. Change @noble/hashes/sha3 to @noble/hashes/sha3.js
- Import maps are not browser-friendly etc
- Before doing this, actually test in real browser
Test in different environments:
- bundler-less browser
- deno
- bun
See how package can fit for JSR.io
Rename / refactor
- crypto / cryptoNode => webcrypto (to match noble-ciphers)
- sha256, sha512 => sha2? not sure yet
- blake2b, blake2s, blake3 => blake?
- ripemd160 => ripemd?
- sha1 => legacy? and add md5??

Maybe also:

Make package ESM-only
Re-audit (need $ funds)

imcotton commented 1 month ago

Any thoughts on adding non-cryptographic hashes? e.g.:

CRC32
Murmur3
xxHash
City
etc...

paulmillr commented 1 month ago

What would be the use case?

imcotton commented 1 month ago

In general non-cryptographic hashes give synchronize call which widely applicable.

CRC32 is good for quick integrity check.

Both Murmur3 and xxHash commonly used in Bloom Filter, however existing widely used NPM packages all using old syntax (ES5, CJS) and have no updates in 5-6 years.

In case of Murmur3, rarely handle utf8 correctly^1. Jumping rabbit hole forks lead to inactive non-resolved issue^2