← Home

@zondax/ledger-stacks

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jleniemmanuel-zondax

Keywords

ZondaxLedgerTypescriptJavascriptStacks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:varuint-bitcoin AI (dependencies): varuint-bitcoin is a well-known Bitcoin varint encoding library; its use is expected in a Ledger/blockchain SDK context. ai
dependencies unvetted-dep:@stacks/transactions AI (dependencies): @stacks/transactions is the official Stacks blockchain transaction library; its use is expected and appropriate for this Ledger Stacks integration package. ai
dependencies unvetted-dep:@ledgerhq/hw-transport AI (dependencies): @ledgerhq/hw-transport is the official Ledger hardware transport library; its use is expected and appropriate for any Ledger hardware wallet SDK. ai

Versions (showing 9 of 9)

Version Deps Published
1.2.0 3 / 20
1.1.2 3 / 20
1.1.1 3 / 20
1.1.0 3 / 22
1.0.4 4 / 22
1.0.3 4 / 22
1.0.2 4 / 22
1.0.1 4 / 22
1.0.0 4 / 22

v1.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: carlosala → jleni (on 2023-03-15, known maintainer) provenance

This version was published by a different npm account (jleni) than the most recent previously approved version (carlosala) on 2023-03-15, but jleni is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: carlosala → jleni (on 2022-11-09, known maintainer) provenance

This version was published by a different npm account (jleni) than the most recent previously approved version (carlosala) on 2022-11-09, but jleni is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jleni → carlosala (on 2022-09-15, known maintainer) provenance

This version was published by a different npm account (carlosala) than the most recent previously approved version (jleni) on 2022-09-15, but carlosala is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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

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