← Home

@ledgerhq/device-signer-kit-solana

This module provides the implementation of the Ledger Solana signer of the Device Management Kit. It enables interaction with the Solana application on a Ledger device including:

15
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:lib/cjs/internal/app-binder/task/context-providers/provideLifiContext.test.js AI (source-diff): Minified vitest test file bundled with CJS build output; standard Ledger SDK packaging pattern. ai
source-diff obfuscated-file:lib/cjs/internal/app-binder/task/context-providers/provideTransactionCheckContext.test.js AI (source-diff): Minified vitest test file bundled with CJS build output; standard Ledger SDK packaging pattern. ai
source-diff obfuscated-file:lib/esm/internal/app-binder/task/context-providers/provideLifiContext.test.js AI (source-diff): Minified vitest test file bundled with ESM build output; standard Ledger SDK packaging pattern. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is expected in a Solana transaction signing library; findings are in compiled test files and reflect normal Solana protocol encoding, not malicious payloads. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in bundled test files is expected for a hardware wallet SDK that handles Solana transaction/instruction data. No malicious payload evidence. ai
dependencies unvetted-dep:@ledgerhq/context-module AI (dependencies): Ledger's own context-module from the same monorepo; legitimate internal dependency. ai
dependencies unvetted-dep:@solana/spl-token AI (dependencies): Official Solana SPL token library maintained by Solana Labs; expected dependency for a Solana signer kit. ai
dependencies unvetted-dep:purify-ts AI (dependencies): purify-ts is a well-known functional programming library (Maybe/Either monads); legitimate dependency for a typed SDK. ai

Versions (showing 15 of 15)

Version Deps Published
1.9.1 11 / 9
1.9.0 11 / 9
1.8.0 11 / 9
1.7.1 11 / 9
1.7.0 11 / 9
1.6.2 11 / 9
1.6.1 11 / 9
1.6.0 11 / 9
1.5.1 11 / 9
1.5.0 11 / 9
1.4.1 11 / 9
1.4.0 11 / 9
1.3.0 11 / 9
1.2.0 11 / 9
1.1.1 6 / 8

v1.9.1

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.9.0

4 findings
HIGH New obfuscated file: lib/cjs/internal/app-binder/task/context-providers/provideLifiContext.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/esm/internal/app-binder/task/context-providers/provideLifiContext.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/cjs/internal/app-binder/task/context-providers/provideTransactionCheckContext.test.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO Has SLSA provenance attestation provenance

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

v1.8.0

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.7.1

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.7.0

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.6.2

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.6.1

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.6.0

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.5.1

1 finding
INFO Has SLSA provenance attestation provenance

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

v1.5.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.4.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.4.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.3.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.2.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.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.