@ledgerhq/device-signer-kit-ethereum
This module provides the implementation of the Ledger Ethereum signer of the Device Management Kit. It enables interaction with the Ethereum application on a Ledger device including:
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:inversify-logger-middleware | AI (phantom-deps): Used in DI container configuration, not directly imported; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:lib/cjs/internal/app-binder/task/SendGetAddressTask.test.js | AI (source-diff): Minified test file output (vitest suite) — long lines are from bundling, not obfuscation. Content is clearly benign test assertions for GetAddressCommand. | ai | |
| source-diff | obfuscated-file:lib/esm/internal/app-binder/task/SendGetAddressTask.test.js | AI (source-diff): Minified ESM test file output (vitest suite) — long lines are from bundling, not obfuscation. Content is clearly benign test assertions for GetAddressCommand. | ai | |
| source-diff | encoded-string-file:lib/cjs/internal/app-binder/command/ProvideNFTInformationCommand.test.js | AI (source-diff): Long hex string is a standard APDU test fixture (NFT metadata + ECDSA signature bytes) in a test file. Not a malicious payload — this pattern is stable for this package. | ai | |
| source-diff | encoded-string-file:lib/esm/internal/app-binder/command/ProvideNFTInformationCommand.test.js | AI (source-diff): Same APDU test fixture in ESM build of the test file. Identical benign pattern as the CJS counterpart — stable false positive for this package. | ai | |
| dependencies | unvetted-dep:purify-ts | AI (dependencies): purify-ts is a well-known functional programming library (Maybe/Either monads) with no security concerns; its use in Ledger SDK is legitimate and expected. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is declared as a dependency and referenced in config files; this is a minor packaging pattern, not a security concern for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.16.0 | 7 / 10 | |
| 1.15.1 | 7 / 10 | |
| 1.15.0 | 7 / 10 | |
| 1.14.0 | 7 / 10 | |
| 1.13.0 | 7 / 10 | |
| 1.12.0 | 7 / 10 | |
| 1.11.1 | 7 / 10 | |
| 1.11.0 | 7 / 10 | |
| 1.10.0 | 7 / 10 | |
| 1.9.5 | 7 / 10 | |
| 1.9.4 | 7 / 10 | |
| 1.9.3 | 7 / 10 | |
| 1.9.2 | 7 / 10 | |
| 1.9.1 | 7 / 10 | |
| 1.9.0 | 7 / 10 | |
| 1.8.0 | 7 / 10 | |
| 1.7.0 | 7 / 10 | |
| 1.6.0 | 7 / 10 | |
| 1.5.0 | 7 / 10 | |
| 1.4.0 | 8 / 10 |
v1.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.12.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.4
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.3
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.