bitcore 0.13.1
A pure and powerful JavaScript Bitcoin library.
bitcore@0.13.1 was published on 2015-08-26. Its manifest declares 7 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All bitcore versions · Permanent reference to 0.13.1 · Latest release
Package specifications
| Version | 0.13.1 |
|---|---|
| License declaration | MIT |
| Published | 2015-08-26T14:25:16.521Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 7 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 4979 |
| Repository forks | 2141 |
Install bitcore 0.13.1
npm install bitcore@0.13.1 pnpm add bitcore@0.13.1 yarn add bitcore@0.13.1
Runtime dependencies
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.
- bn.js@2.0.4 — direct
- brorand@1.1.0 — indirect
- bs58@2.0.0 — direct
- elliptic@3.0.3 — direct
- hash.js@1.0.2 — direct
- inherits@2.0.1 — direct
- lodash@3.10.1 — direct
- sha512@0.0.1 — 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.
| Code-Review | 8/10 — Found 5/6 approved changesets -- score normalized to 8 |
|---|---|
| Maintained | 10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Binary-Artifacts | 9/10 — binaries present in source code |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
Evidence and freshness
- https://registry.npmjs.org/bitcore/0.13.1 — retrieved 2026-10-30T12:36:22.779Z
- https://api.deps.dev/v3/systems/npm/packages/bitcore/versions/0.13.1 — retrieved 2026-10-30T12:36:23.199Z
- https://api.deps.dev/v3/systems/npm/packages/bitcore/versions/0.13.1:dependencies — retrieved 2026-10-30T12:36:23.237Z
- https://api.deps.dev/v3/projects/github.com%2Fbitpay%2Fbitcore — retrieved 2026-10-30T09:39:37.058Z