@ledgerhq/device-react
Ledger Live device react module
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ledgerhq/device-core | AI (dependencies): @ledgerhq/device-core is a first-party LedgerHQ package from the same ledger-live monorepo; dependency is expected and appropriate. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes from a CI bot account in their monorepo; lack of Sigstore provenance is consistent across their releases and not a security concern for this established package. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.6.8 | 1 / 12 | |
| 0.6.7 | 1 / 12 | |
| 0.6.6 | 1 / 12 | |
| 0.6.5 | 1 / 12 | |
| 0.6.4 | 1 / 12 | |
| 0.6.3 | 1 / 12 | |
| 0.6.2 | 1 / 12 | |
| 0.6.1 | 1 / 12 | |
| 0.6.0 | 1 / 12 | |
| 0.5.4 | 1 / 10 | |
| 0.5.3 | 1 / 10 | |
| 0.5.2 | 1 / 10 | |
| 0.5.1 | 1 / 10 | |
| 0.5.0 | 1 / 10 | |
| 0.4.6 | 1 / 10 | |
| 0.4.5 | 1 / 10 | |
| 0.4.4 | 1 / 10 | |
| 0.4.3 | 1 / 10 | |
| 0.4.2 | 1 / 10 | |
| 0.4.1 | 1 / 10 | |
| 0.4.0 | 1 / 10 | |
| 0.3.7 | 1 / 8 | |
| 0.3.6 | 1 / 8 | |
| 0.3.5 | 1 / 8 | |
| 0.3.4 | 1 / 8 | |
| 0.3.3 | 1 / 8 | |
| 0.3.2 | 1 / 8 | |
| 0.3.1 | 1 / 8 | |
| 0.3.0 | 1 / 8 | |
| 0.2.46 | 1 / 8 | |
| 0.2.45 | 1 / 8 | |
| 0.2.44 | 1 / 8 | |
| 0.2.43 | 1 / 8 | |
| 0.2.42 | 1 / 8 | |
| 0.2.41 | 1 / 8 | |
| 0.2.40 | 1 / 8 | |
| 0.2.39 | 1 / 8 | |
| 0.2.38 | 1 / 8 | |
| 0.2.37 | 1 / 8 | |
| 0.2.36 | 1 / 8 | |
| 0.2.35 | 1 / 8 | |
| 0.2.34 | 1 / 8 | |
| 0.2.33 | 1 / 8 | |
| 0.2.32 | 1 / 8 | |
| 0.2.31 | 1 / 8 | |
| 0.2.30 | 1 / 8 | |
| 0.2.29 | 1 / 8 | |
| 0.2.28 | 1 / 8 | |
| 0.2.27 | 1 / 8 | |
| 0.2.26 | 1 / 8 | |
| 0.2.25 | 1 / 8 | |
| 0.2.24 | 1 / 8 | |
| 0.2.23 | 1 / 8 | |
| 0.2.22 | 1 / 8 | |
| 0.2.21 | 1 / 8 | |
| 0.2.20 | 1 / 8 | |
| 0.2.19 | 1 / 8 | |
| 0.2.18 | 1 / 8 | |
| 0.2.17 | 1 / 8 | |
| 0.2.16 | 1 / 8 | |
| 0.2.15 | 1 / 8 | |
| 0.2.14 | 1 / 8 | |
| 0.2.13 | 1 / 8 | |
| 0.2.12 | 1 / 8 | |
| 0.2.11 | 1 / 8 | |
| 0.2.10 | 1 / 8 | |
| 0.2.9 | 1 / 8 | |
| 0.2.8 | 1 / 8 | |
| 0.2.7 | 1 / 8 | |
| 0.2.6 | 1 / 8 | |
| 0.2.5 | 1 / 8 | |
| 0.2.4 | 1 / 8 | |
| 0.2.3 | 1 / 8 | |
| 0.2.2 | 1 / 8 | |
| 0.2.1 | 1 / 8 | |
| 0.2.0 | 1 / 8 | |
| 0.1.2 | 1 / 8 | |
| 0.1.1 | 1 / 8 | |
| 0.1.0 | 1 / 8 |
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
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.
v0.1.2
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.1.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.1.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.