← Home

@ledgerhq/cryptoassets

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

Ledger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in this package is standard blockchain address encoding (hex→base58check for TRC10 token addresses). Not a malicious payload pattern; stable false positive for this crypto-assets library. ai
phantom-deps phantom-dep:@ledgerhq/types-live AI (phantom-deps): Same-org dependency declared for type compatibility; not a security concern for this package. ai
dependencies unvetted-dep:@ledgerhq/errors AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ monorepo. Not a third-party unknown. ai
semgrep semgrep:shady-links-tlds AI (semgrep): This package is a crypto-assets registry that legitimately contains blockchain explorer URLs with non-traditional TLDs (e.g., .xyz). These are data entries, not executable network calls. Stable false positive for this package. ai
dependencies unvetted-dep:@ledgerhq/types-live AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ monorepo. Not a third-party unknown. ai
dependencies unvetted-dep:@ledgerhq/live-env AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ monorepo. Not a third-party unknown. ai
dependencies unvetted-dep:@ledgerhq/logs AI (dependencies): First-party @ledgerhq/* dependency from the same LedgerHQ monorepo. Not a third-party unknown. ai

Versions (showing 42 of 42)

Version Deps Published
13.50.0 8 / 16
13.48.0 8 / 16
13.47.0 8 / 16
13.46.2 8 / 16
13.46.1 8 / 16
13.46.0 8 / 16
13.45.0 8 / 16
13.44.0 8 / 16
13.43.0 8 / 16
13.42.0 8 / 16
13.41.0 8 / 16
13.40.0 8 / 16
13.39.1 8 / 16
13.39.0 8 / 16
13.38.1 7 / 16
13.38.0 7 / 16
13.37.1 7 / 16
13.37.0 7 / 16
13.36.0 7 / 14
13.35.1 7 / 14
13.35.0 7 / 14
13.34.1 7 / 14
13.34.0 7 / 14
13.33.0 7 / 15
13.32.0 7 / 15
13.31.0 5 / 9
13.30.0 4 / 10
13.29.0 4 / 10
13.28.0 4 / 10
13.27.0 4 / 10
13.26.0 4 / 10
13.25.0 4 / 10
13.24.0 4 / 10
13.23.0 4 / 10
13.22.0 4 / 10
13.21.0 4 / 10
13.20.0 4 / 10
13.19.0 4 / 10
13.18.1 4 / 10
13.18.0 4 / 10
13.17.0 4 / 10
13.16.0 4 / 10

v13.50.0

1 finding
LOW No provenance attestation provenance

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

v13.48.0

1 finding
LOW No provenance attestation provenance

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

v13.47.0

1 finding
LOW No provenance attestation provenance

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

v13.46.2

1 finding
LOW No provenance attestation provenance

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

v13.46.1

1 finding
LOW No provenance attestation provenance

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

v13.46.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.

v13.45.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.

v13.44.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.

v13.43.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.

v13.31.0

1 finding
LOW No provenance attestation provenance

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

v13.30.0

1 finding
LOW No provenance attestation provenance

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

v13.29.0

1 finding
LOW No provenance attestation provenance

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

v13.28.0

1 finding
LOW No provenance attestation provenance

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

v13.27.0

1 finding
LOW No provenance attestation provenance

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

v13.26.0

1 finding
LOW No provenance attestation provenance

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

v13.25.0

1 finding
LOW No provenance attestation provenance

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

v13.24.0

1 finding
LOW No provenance attestation provenance

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

v13.23.0

1 finding
LOW No provenance attestation provenance

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

v13.22.0

1 finding
LOW No provenance attestation provenance

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

v13.21.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.

v13.20.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.

v13.19.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.

v13.18.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.

v13.18.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.

v13.17.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.

v13.16.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.