bs58
Base 58 encoding / decoding
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition within cryptocoinjs org; junderw is a well-established npm publisher (141 approved packages, 2593 days on npm). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): junderw is a known cryptocoinjs contributor; legitimate org-internal handoff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): dcousens removed as part of legitimate maintainer transition within cryptocoinjs. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable Base58 library doesn't need frequent updates; dormancy is expected for mature crypto utility. | ai |
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-02-17. 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.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.