@ledgerhq/coin-aleo
Ledger Aleo Coin integration
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/__tests__/fixtures/api.fixture.ts | AI (source-diff): Long strings are Aleo blockchain field elements and ciphertext values in test fixtures — expected for this coin integration package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is declared as a dep and used in config/build tooling in this monorepo package; phantom-dep finding is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org dep used transitively in this monorepo package; phantom-dep finding is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/live-env | AI (phantom-deps): Same-org dep used transitively in this monorepo package; phantom-dep finding is a stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI bot without Sigstore provenance; consistent across their package ecosystem and not a security concern. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-live | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/cryptoassets | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-network | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(tlv, 'hex') is standard TLV decoding for hardware wallet signing protocols; not obfuscation or malicious payload. Expected pattern for Ledger coin integrations. | ai | |
| dependencies | unvetted-dep:@ledgerhq/types-cryptoassets | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-module-framework | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/ledger-wallet-framework | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-promise | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/logs | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/errors | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/devices | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-env | AI (dependencies): Internal @ledgerhq scoped package from the same organization; unvetted status is a registry gap, not a risk signal. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.13.1 | 15 / 11 | |
| 1.13.0 | 15 / 11 | |
| 1.12.0 | 15 / 11 | |
| 1.11.0 | 15 / 11 | |
| 1.10.2 | 15 / 10 | |
| 1.10.1 | 15 / 10 | |
| 1.10.0 | 15 / 10 | |
| 1.9.0 | 15 / 10 | |
| 1.8.0 | 15 / 9 | |
| 1.7.0 | 15 / 9 | |
| 1.6.0 | 14 / 9 | |
| 1.5.0 | 14 / 9 | |
| 1.4.0 | 14 / 8 | |
| 1.3.0 | 11 / 8 | |
| 1.2.0 | 10 / 8 | |
| 1.1.3 | 10 / 8 | |
| 1.1.2 | 10 / 8 | |
| 1.1.1 | 10 / 8 | |
| 1.1.0 | 10 / 8 |
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.