← Home

@celo/wallet-base

4
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

app-tooling

Keywords

celoblockchainsdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/debug AI (phantom-deps): @types/debug is legitimately declared as a runtime dependency (unusual but intentional); phantom-dep finding is a stable false positive for this package. ai
phantom-deps phantom-dep:bignumber.js AI (phantom-deps): bignumber.js is referenced in config files for this SDK package; phantom-dep finding is a stable false positive. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in signing-utils.js is standard ECDSA signature encoding (r/s components to 32-byte buffers), not a malicious payload. This pattern is inherent to any Ethereum signing library. ai

Versions (showing 4 of 4)

Version Deps Published
8.0.3 11 / 3
8.0.2 11 / 3
8.0.1 11 / 3
8.0.0 11 / 3

v8.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.