bip32 5.0.0
A BIP32 compatible library
bip32@5.0.0 was published on 2025-10-02. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.0.0.
All bip32 versions · Permanent reference to 5.0.0 · Latest release
Package specifications
| Version | 5.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2025-10-02T00:54:59.608Z |
| Node.js requirement | >=18.0.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 53.12 KiB |
| Published file count | 18 |
| Package type | module |
| ES module entry | ./src/esm/index.js |
| Default entry | ./src/cjs/index.cjs |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 196 |
| Repository forks | 133 |
Install bip32 5.0.0
npm install bip32@5.0.0 pnpm add bip32@5.0.0 yarn add bip32@5.0.0
Runtime dependencies
- wif ^5.0.0
- valibot ^0.37.0
- @scure/base ^1.1.1
- @noble/hashes ^1.2.0
- uint8array-tools ^0.0.8
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @noble/hashes@1.8.0 — direct
- @scure/base@1.2.6 — direct
- base-x@5.0.1 — indirect
- bs58@6.0.0 — indirect
- bs58check@4.0.0 — indirect
- uint8array-tools@0.0.8 — direct
- valibot@0.37.0 — direct
- wif@5.0.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 5/10 — Found 5/9 approved changesets -- score normalized to 5 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/bip32/5.0.0 — retrieved 2026-10-30T18:28:18.156Z
- https://api.deps.dev/v3/projects/github.com%2Fbitcoinjs%2Fbip32 — retrieved 2026-10-30T14:05:58.964Z
- https://api.deps.dev/v3/systems/npm/packages/bip32/versions/5.0.0 — retrieved 2026-10-30T18:28:18.556Z
- https://api.deps.dev/v3/systems/npm/packages/bip32/versions/5.0.0:dependencies — retrieved 2026-10-30T18:28:18.569Z