@ledgerhq/hw-app-xrp
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): Buffer.from(rawTxHex, 'hex') is standard hex-to-buffer conversion for XRP transaction signing — core functionality of this hardware wallet app, not a malicious payload. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.37.3 | 2 / 10 | |
| 6.37.2 | 2 / 10 | |
| 6.37.1 | 2 / 10 | |
| 6.37.0 | 2 / 10 | |
| 6.36.0 | 2 / 10 | |
| 6.35.0 | 2 / 10 | |
| 6.34.0 | 2 / 10 | |
| 6.33.0 | 2 / 10 | |
| 6.32.10 | 2 / 9 | |
| 6.32.9 | 2 / 9 | |
| 6.32.8 | 2 / 9 | |
| 6.32.7 | 2 / 9 | |
| 6.32.6 | 2 / 9 | |
| 6.32.5 | 2 / 9 | |
| 6.32.4 | 2 / 9 | |
| 6.32.3 | 2 / 9 | |
| 6.32.2 | 2 / 9 | |
| 6.32.1 | 2 / 9 | |
| 6.32.0 | 2 / 9 | |
| 6.31.2 | 2 / 10 | |
| 6.31.1 | 2 / 10 |
v6.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.