@ledgerhq/hw-app-aptos
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:lib-es/Aptos.d.ts | AI (source-diff): The long hex string is a JSDoc @example showing a sample transaction buffer for signTransaction(). It is documentation, not a payload, and is stable across versions of this package. | ai | |
| source-diff | encoded-string-file:lib/Aptos.d.ts | AI (source-diff): Same JSDoc @example hex string in the CJS declaration file. Benign documentation pattern stable for this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/hw-transport | AI (dependencies): @ledgerhq/hw-transport is a core sibling package in the LedgerHQ ecosystem, used as the transport abstraction across all hw-app-* packages. This dependency is expected and stable. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via ldg-github-ci CI pipeline; lack of Sigstore provenance is consistent across their packages and not a security concern for this established publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 6.38.3 | 4 / 10 | |
| 6.38.2 | 4 / 10 | |
| 6.38.1 | 4 / 10 | |
| 6.38.0 | 4 / 10 | |
| 6.37.1 | 4 / 10 | |
| 6.37.0 | 4 / 10 | |
| 6.36.0 | 4 / 10 | |
| 6.35.0 | 4 / 10 | |
| 6.34.12 | 4 / 9 | |
| 6.34.11 | 4 / 9 | |
| 6.34.10 | 4 / 9 | |
| 6.34.9 | 4 / 9 | |
| 6.34.8 | 4 / 9 | |
| 6.34.7 | 4 / 9 | |
| 6.34.6 | 4 / 9 | |
| 6.34.5 | 4 / 9 | |
| 6.34.4 | 4 / 9 | |
| 6.34.3 | 4 / 9 | |
| 6.34.2 | 4 / 10 | |
| 6.34.1 | 4 / 10 |
v6.38.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.38.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.37.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.0
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.34.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.34.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.