← Home

@exodus/bip322-js

npm Repository Homepage
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

joshuabot

Keywords

bip322bitcoinjsjavascripttypescriptno-WASM

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@exodus/crypto AI (dependencies): First-party Exodus org dependency; consistent with the package's ecosystem and author. ai
dependencies unvetted-dep:minimalistic-assert AI (dependencies): minimalistic-assert is a widely-used, stable utility; no risk for this package. ai
provenance no-provenance AI (provenance): Exodus monorepo explicitly sets provenance:false; consistent across their packages. ai

Versions (showing 4 of 4)

Version Deps Published
3.2.1 9 / 5
3.2.0 9 / 5
3.1.0 5 / 10
3.0.0 5 / 10

v3.2.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.

v3.2.0

1 finding
INFO No provenance attestation provenance

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

v3.1.0

1 finding
INFO No provenance attestation provenance

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

v3.0.0

1 finding
INFO No provenance attestation provenance

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