@ledgerhq/live-countervalues-react
Ledger Live countervalues 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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ledgerhq/live-hooks | AI (dependencies): Same-org (@ledgerhq) dependency from the LedgerHQ monorepo; low risk for this package family. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/cryptoassets | AI (phantom-deps): Same-org scoped package declared as dependency but not directly imported; minor packaging issue, not a security concern for this LedgerHQ monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ CI publishes many packages without Sigstore provenance; package identity is confirmed by org scope, repo URL, and version history. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 7 / 10 | |
| 0.14.4 | 7 / 10 | |
| 0.14.3 | 7 / 10 | |
| 0.14.2 | 7 / 10 | |
| 0.14.1 | 7 / 10 | |
| 0.14.0 | 7 / 10 | |
| 0.13.0 | 7 / 10 | |
| 0.12.0 | 7 / 10 | |
| 0.11.0 | 8 / 9 | |
| 0.10.3 | 8 / 9 | |
| 0.10.2 | 8 / 9 | |
| 0.10.1 | 8 / 9 | |
| 0.10.0 | 8 / 9 | |
| 0.9.3 | 8 / 9 | |
| 0.9.2 | 8 / 9 | |
| 0.9.1 | 8 / 9 | |
| 0.9.0 | 8 / 9 | |
| 0.8.0 | 8 / 9 | |
| 0.7.7 | 8 / 7 | |
| 0.7.6 | 8 / 7 | |
| 0.7.5 | 8 / 7 | |
| 0.7.4 | 8 / 7 | |
| 0.7.3 | 8 / 7 | |
| 0.7.2 | 8 / 7 | |
| 0.7.1 | 8 / 7 | |
| 0.7.0 | 8 / 7 | |
| 0.6.2 | 8 / 7 | |
| 0.6.1 | 8 / 7 | |
| 0.6.0 | 8 / 7 | |
| 0.5.1 | 8 / 7 | |
| 0.5.0 | 8 / 7 | |
| 0.4.0 | 8 / 7 | |
| 0.3.0 | 8 / 7 | |
| 0.2.44 | 8 / 7 | |
| 0.2.43 | 8 / 7 | |
| 0.2.42 | 8 / 7 | |
| 0.2.41 | 8 / 7 | |
| 0.2.40 | 8 / 7 | |
| 0.2.39 | 8 / 7 | |
| 0.2.38 | 8 / 7 | |
| 0.2.37 | 8 / 7 | |
| 0.2.36 | 8 / 7 | |
| 0.2.35 | 8 / 7 | |
| 0.2.34 | 8 / 7 | |
| 0.2.33 | 8 / 7 | |
| 0.2.32 | 8 / 7 |
v0.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.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.12.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.11.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.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
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.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.