@ledgerhq/hw-app-sui
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 decoding is used for Ledger CAL service token descriptors and signatures — standard hardware wallet protocol handling. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI without Sigstore provenance; consistent across their package ecosystem and not a meaningful risk signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.11.1 | 4 / 11 | |
| 1.11.0 | 4 / 11 | |
| 1.10.1 | 7 / 11 | |
| 1.10.0 | 7 / 11 | |
| 1.9.0 | 1 / 10 | |
| 1.8.0 | 1 / 10 | |
| 1.7.0 | 1 / 10 | |
| 1.6.0 | 1 / 10 | |
| 1.5.0 | 1 / 10 | |
| 1.4.0 | 1 / 9 | |
| 1.3.0 | 1 / 9 | |
| 1.2.0 | 1 / 9 |
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.