← Home

@bitcoinerlab/descriptors-scure

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

jl.landabaso

Keywords

bitcoindescriptorsminiscriptpsbtscurenoblebtc-signerbip32

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@scure/base AI (phantom-deps): @scure/base is a legitimate declared dependency; phantom-dep fires because it's used transitively, not directly imported. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): @noble/hashes is a legitimate declared dependency; phantom-dep fires because it's used transitively, not directly imported. ai

Versions (showing 8 of 8)

Version Deps Published
3.1.7 6 / 0
3.1.6 6 / 0
3.1.5 6 / 0
3.1.4 6 / 0
3.1.3 5 / 0
3.1.2 5 / 0
3.1.1 5 / 0
3.1.0 5 / 0

v3.1.7

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.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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