@ledgerhq/hw-app-canton
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-to-buffer conversion (Buffer.from(x, 'hex')) is a core operation in hardware wallet transport libraries for encoding transaction data. No malicious payload hiding — this is standard protocol communication code. | ai | |
| provenance | no-provenance | AI (provenance): Published by LedgerHQ's CI account (ldg-github-ci) from the well-known ledger-live monorepo. Lack of Sigstore provenance is acceptable given the established publisher track record. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.12.2 | 4 / 12 | |
| 0.12.1 | 4 / 12 | |
| 0.12.0 | 4 / 12 | |
| 0.11.0 | 3 / 11 | |
| 0.10.1 | 3 / 11 | |
| 0.10.0 | 3 / 11 | |
| 0.9.0 | 3 / 11 | |
| 0.8.0 | 3 / 11 | |
| 0.7.3 | 3 / 10 | |
| 0.7.2 | 3 / 10 | |
| 0.7.1 | 3 / 10 | |
| 0.7.0 | 3 / 10 | |
| 0.6.0 | 3 / 10 | |
| 0.5.1 | 3 / 10 | |
| 0.5.0 | 3 / 10 | |
| 0.4.0 | 3 / 10 | |
| 0.3.0 | 4 / 10 | |
| 0.2.2 | 4 / 9 | |
| 0.2.1 | 4 / 9 | |
| 0.2.0 | 4 / 9 |
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.
v0.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.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.