@ledgerhq/react-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ledgerhq/crypto-icons-ui | AI (dependencies): First-party LedgerHQ sibling package from the same monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/icons-ui | AI (dependencies): First-party LedgerHQ dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/ui-shared | AI (dependencies): First-party LedgerHQ dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ CI pipeline consistently publishes without Sigstore provenance; stable pattern across 161 approved packages. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): react-is is a declared runtime dep used transitively by styled-components/react-select; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.52.0 | 15 / 62 | |
| 0.51.0 | 15 / 62 | |
| 0.50.0 | 15 / 50 | |
| 0.45.0 | 15 / 55 | |
| 0.44.1 | 15 / 55 | |
| 0.44.0 | 15 / 55 | |
| 0.43.0 | 16 / 56 | |
| 0.42.0 | 16 / 56 | |
| 0.41.1 | 18 / 56 | |
| 0.40.0 | 18 / 56 | |
| 0.38.0 | 18 / 54 | |
| 0.37.0 | 18 / 54 | |
| 0.35.0 | 18 / 54 | |
| 0.34.0 | 18 / 54 | |
| 0.30.0 | 18 / 54 | |
| 0.29.0 | 18 / 54 | |
| 0.26.0 | 18 / 54 | |
| 0.25.0 | 17 / 54 |
v0.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.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.37.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.35.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.34.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.30.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.29.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.26.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.25.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.