← Home

@ledgerhq/coin-kaspa

Ledger Kaspa Coin integration

30
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

LedgerLedgerWalletHardware WalletKaspaKASBlockDAG

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@bitcoinerlab/secp256k1 AI (dependencies): Standard secp256k1 cryptographic library appropriate for a Kaspa/Bitcoin-family coin integration; expected dependency for this package's purpose. ai
phantom-deps phantom-dep:expect AI (phantom-deps): Declared dependency used in test/config context; not a security concern for this package. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Declared dependency referenced in config files; benign for this package. ai
phantom-deps phantom-dep:invariant AI (phantom-deps): Declared dependency referenced in config files; benign for this package. ai
phantom-deps phantom-dep:lru-cache AI (phantom-deps): Declared dependency referenced in config files; benign for this package. ai
phantom-deps phantom-dep:@ledgerhq/devices AI (phantom-deps): Same-org @ledgerhq scoped package; phantom detection in monorepo is expected. Not a security concern. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding of xpub/public keys is standard and expected in a cryptocurrency wallet library. No malicious payload present; this is a stable false positive for this package. ai
phantom-deps phantom-dep:@ledgerhq/cryptoassets AI (phantom-deps): Same-org @ledgerhq scoped package; phantom detection in monorepo is expected. Not a security concern. ai
phantom-deps phantom-dep:eip55 AI (phantom-deps): Phantom dep in a monorepo context; declared for config/test use. Not a security concern for this package. ai
phantom-deps phantom-dep:prando AI (phantom-deps): Phantom dep in a monorepo context; declared for config/test use. Not a security concern for this package. ai
phantom-deps phantom-dep:bip32-path AI (phantom-deps): Phantom dep in a monorepo context; declared for config/test use. Not a security concern for this package. ai
phantom-deps phantom-dep:@ledgerhq/logs AI (phantom-deps): Same-org @ledgerhq scoped package; phantom detection in monorepo is expected. Not a security concern. ai

Versions (showing 30 of 30)

Version Deps Published
1.15.0 20 / 15
1.14.2 20 / 15
1.14.1 20 / 15
1.14.0 21 / 15
1.13.2 21 / 15
1.13.1 21 / 15
1.13.0 21 / 15
1.12.0 21 / 15
1.11.1 21 / 13
1.11.0 21 / 13
1.10.0 20 / 13
1.9.0 20 / 13
1.8.2 20 / 12
1.8.1 20 / 12
1.8.0 20 / 12
1.7.3 20 / 12
1.7.2 20 / 12
1.7.1 20 / 12
1.7.0 20 / 12
1.6.2 20 / 11
1.6.1 20 / 11
1.6.0 20 / 11
1.5.1 20 / 11
1.5.0 20 / 11
1.4.1 20 / 12
1.4.0 20 / 12
1.3.0 20 / 12
1.2.0 20 / 12
1.1.1 20 / 12
1.1.0 20 / 12

v1.15.0

1 finding
LOW No provenance attestation provenance

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

v1.14.2

1 finding
LOW No provenance attestation provenance

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

v1.14.1

1 finding
LOW No provenance attestation provenance

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

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.2

1 finding
LOW No provenance attestation provenance

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

v1.13.1

1 finding
LOW No provenance attestation provenance

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

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

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

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.3

1 finding
LOW No provenance attestation provenance

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

v1.7.2

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

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

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