wif
Bitcoin Wallet Import Format (WIF) decoding/encoding module
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Legitimate transition within bitcoinjs org: dcousens → junderw/fanatid/jprichardson are all known bitcoinjs maintainers. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from dcousens to junderw is a known bitcoinjs org maintainer transition; junderw has strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (fanatid, jprichardson, junderw) are established bitcoinjs ecosystem contributors. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): dcousens removal is part of documented bitcoinjs maintainer transition; repo remains in same GitHub org. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 1 / 7 | |
| 4.0.0 | 1 / 4 | |
| 3.0.1 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.6 | 1 / 3 | |
| 2.0.5 | 1 / 3 | |
| 2.0.4 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.2 | 1 / 3 | |
| 2.0.1 | 1 / 4 | |
| 2.0.0 | 1 / 4 | |
| 1.2.1 | 1 / 4 | |
| 1.2.0 | 1 / 4 | |
| 1.1.2 | 1 / 4 | |
| 1.1.1 | 1 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.0.1 | 1 / 4 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
3 findingsAll previous maintainers (dcousens) were replaced by new maintainers (fanatid, jprichardson, junderw). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2023-08-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.