bitcoin-address-validation 1.0.1

Validate any Bitcoin address - Bech32, P2SH and P2PKH

bitcoin-address-validation@1.0.1 was published on 2020-02-04. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All bitcoin-address-validation versions · Permanent reference to 1.0.1 · Latest release

Package specifications

Version1.0.1
License declarationMIT
Published2020-02-04T14:35:21.623Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size97.88 KiB
Published file count8
Package typeNot declared
ES module entry./lib/index.esm.js
Default entry./lib/index.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies35
Repository stars125
Repository forks27

Install bitcoin-address-validation 1.0.1

npm install bitcoin-address-validation@1.0.1
pnpm add bitcoin-address-validation@1.0.1
yarn add bitcoin-address-validation@1.0.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.

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-Review1/10 — Found 3/27 approved changesets -- score normalized to 1
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness