@atcute/multibase
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are documented native base58 bindings compiled with Zig; stable pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves platform-specific prebuild path only; not arbitrary module loading. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 1 / 4 | |
| 1.1.8 | 1 / 3 | |
| 1.1.7 | 1 / 3 | |
| 1.1.6 | 1 / 1 | |
| 1.1.5 | 1 / 1 | |
| 1.1.4 | 1 / 1 |
v1.2.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/base58.node • prebuilds/linux-arm64-glibc/base58.node • prebuilds/linux-arm64-musl/base58.node • prebuilds/linux-x64-glibc/base58.node • prebuilds/linux-x64-musl/base58.node • prebuilds/win32-x64/base58.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.