bitcoinjs-message 2.1.4
bitcoinjs-message
bitcoinjs-message@2.1.4 was published on 2020-12-23. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=0.10.
All bitcoinjs-message versions · Permanent reference to 2.1.4 · Latest release
Package specifications
| Version | 2.1.4 |
|---|---|
| License declaration | MIT |
| Published | 2020-12-23T23:16:48.530Z |
| Node.js requirement | >=0.10 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 11.12 KiB |
| Published file count | 6 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 69 |
| Repository stars | 133 |
| Repository forks | 83 |
Install bitcoinjs-message 2.1.4
npm install bitcoinjs-message@2.1.4 pnpm add bitcoinjs-message@2.1.4 yarn add bitcoinjs-message@2.1.4
Runtime dependencies
- bech32 ^1.1.3
- bs58check ^2.1.2
- secp256k1 ^3.0.1
- create-hash ^1.1.2
- buffer-equals ^1.0.3
- varuint-bitcoin ^1.0.1
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.
- bech32@1.1.4 — direct
- bs58check@2.1.2 — direct
- buffer-equals@1.0.4 — direct
- create-hash@1.2.0 — direct
- secp256k1@3.8.1 — direct
- varuint-bitcoin@1.1.2 — direct
- bs58@4.0.1 — indirect
- safe-buffer@5.2.1 — indirect
- cipher-base@1.0.7 — indirect
- inherits@2.0.4 — indirect
- md5.js@1.3.5 — indirect
- ripemd160@2.0.3 — indirect
- sha.js@2.4.12 — indirect
- bindings@1.5.0 — indirect
- bip66@1.1.5 — indirect
- bn.js@4.12.5 — indirect
- drbg.js@1.0.1 — indirect
- elliptic@6.6.1 — indirect
- nan@2.30.0 — indirect
- base-x@3.0.11 — indirect
- to-buffer@1.2.2 — indirect
- hash-base@3.1.2 — indirect
- file-uri-to-path@1.0.0 — indirect
- browserify-aes@1.2.0 — indirect
- create-hmac@1.1.7 — indirect
- brorand@1.1.0 — indirect
- hash.js@1.1.7 — indirect
- hmac-drbg@1.0.1 — indirect
- minimalistic-assert@1.0.1 — indirect
- minimalistic-crypto-utils@1.0.1 — indirect
- isarray@2.0.5 — indirect
- typed-array-buffer@1.0.3 — indirect
- readable-stream@2.3.8 — indirect
- buffer-xor@1.0.3 — indirect
- evp_bytestokey@1.0.3 — indirect
- call-bound@1.0.4 — indirect
- es-errors@1.3.0 — indirect
- is-typed-array@1.1.15 — indirect
- core-util-is@1.0.3 — indirect
- isarray@1.0.0 — indirect
- process-nextick-args@2.0.1 — indirect
- safe-buffer@5.1.2 — indirect
- string_decoder@1.1.1 — indirect
- util-deprecate@1.0.2 — indirect
- call-bind-apply-helpers@1.0.2 — indirect
- get-intrinsic@1.3.1 — indirect
- which-typed-array@1.1.24 — indirect
- safe-buffer@5.1.2 — indirect
- function-bind@1.1.2 — indirect
- async-function@1.0.0 — indirect
- async-generator-function@1.0.0 — indirect
- es-define-property@1.0.1 — indirect
- es-object-atoms@1.1.2 — indirect
- generator-function@2.0.1 — indirect
- get-proto@1.0.1 — indirect
- gopd@1.2.0 — indirect
- has-symbols@1.1.0 — indirect
- hasown@2.0.4 — indirect
- math-intrinsics@1.1.0 — indirect
- available-typed-arrays@1.0.7 — indirect
- call-bind@1.0.9 — indirect
- for-each@0.3.5 — indirect
- has-tostringtag@1.0.2 — indirect
- dunder-proto@1.0.1 — indirect
- possible-typed-array-names@1.1.0 — indirect
- set-function-length@1.2.2 — indirect
- is-callable@1.2.7 — indirect
- define-data-property@1.1.4 — indirect
- has-property-descriptors@1.0.2 — indirect
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.
| Code-Review | 3/10 — Found 5/13 approved changesets -- score normalized to 3 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/bitcoinjs-message/2.1.4 — retrieved 2026-10-30T14:07:24.885Z
- https://api.deps.dev/v3/systems/npm/packages/bitcoinjs-message/versions/2.1.4 — retrieved 2026-10-30T14:07:25.421Z
- https://api.deps.dev/v3/systems/npm/packages/bitcoinjs-message/versions/2.1.4:dependencies — retrieved 2026-10-30T14:07:25.456Z
- https://api.deps.dev/v3/projects/github.com%2Fbitcoinjs%2Fbitcoinjs-message — retrieved 2026-10-30T14:07:26.009Z