@ledgerhq/native-ui
Ledger Live - Mobile UI
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): LedgerHQ CI pipeline consistently publishes without Sigstore provenance; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:rn-range-slider | AI (dependencies): Known React Native slider library; no malware indicators, stable dependency for this UI package. | ai | |
| dependencies | unvetted-dep:react-native-modal | AI (dependencies): Well-known React Native modal library; no malware indicators, stable dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/crypto-icons-ui | AI (dependencies): First-party LedgerHQ package; safe to accept for this package. | ai | |
| phantom-deps | phantom-dep:stylis | AI (phantom-deps): stylis is explicitly listed as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.63.0 | 6 / 102 | |
| 0.62.0 | 6 / 102 | |
| 0.61.0 | 6 / 100 | |
| 0.60.0 | 6 / 101 | |
| 0.59.0 | 6 / 101 | |
| 0.58.0 | 7 / 101 | |
| 0.56.0 | 7 / 101 | |
| 0.54.0 | 7 / 108 | |
| 0.53.0 | 7 / 108 | |
| 0.51.0 | 6 / 110 | |
| 0.47.0 | 8 / 109 | |
| 0.41.0 | 8 / 109 | |
| 0.40.0 | 8 / 109 | |
| 0.38.0 | 7 / 109 | |
| 0.37.0 | 7 / 109 | |
| 0.35.0 | 7 / 95 | |
| 0.34.1 | 7 / 95 | |
| 0.34.0 | 7 / 95 |
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.