@types/bs58
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.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/base-x | AI (phantom-deps): Type definition packages declare deps by convention, not direct import. @types/base-x is a legitimate transitive type dependency for @types/bs58. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped packages published via the types publisher consistently lack Sigstore provenance; this is expected for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a stub @types/ definition package — tiny payload, no README code, no repo URL are all expected and normal for this package type. | ai | |
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Stub @types/ packages declare the upstream as a dependency without importing it in code; this is the standard forwarding pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 1 / 0 | |
| 4.0.4 | 2 / 0 | |
| 4.0.3 | 2 / 0 | |
| 4.0.2 | 1 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.