@ledgerhq/live-countervalues
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): LedgerHQ publishes from a monorepo CI pipeline; lack of Sigstore provenance is consistent across their ecosystem and not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/cryptoassets | AI (phantom-deps): @ledgerhq/cryptoassets is declared as a dependency but not directly imported — a packaging artifact from the monorepo build, not a security concern. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 7 / 7 | |
| 0.22.1 | 7 / 7 | |
| 0.22.0 | 7 / 6 | |
| 0.21.0 | 7 / 6 | |
| 0.20.0 | 7 / 6 | |
| 0.19.0 | 7 / 6 | |
| 0.18.6 | 8 / 6 | |
| 0.18.5 | 8 / 6 | |
| 0.18.4 | 8 / 6 | |
| 0.18.3 | 8 / 6 | |
| 0.18.2 | 8 / 6 | |
| 0.18.1 | 8 / 6 | |
| 0.18.0 | 8 / 6 | |
| 0.17.0 | 8 / 6 | |
| 0.16.0 | 8 / 6 | |
| 0.15.1 | 8 / 6 | |
| 0.15.0 | 8 / 6 | |
| 0.14.0 | 8 / 5 | |
| 0.13.0 | 8 / 5 | |
| 0.12.2 | 8 / 5 | |
| 0.12.1 | 8 / 5 | |
| 0.12.0 | 8 / 5 | |
| 0.11.1 | 8 / 5 | |
| 0.11.0 | 8 / 5 | |
| 0.10.5 | 8 / 4 | |
| 0.10.4 | 8 / 4 | |
| 0.10.3 | 8 / 4 | |
| 0.10.2 | 8 / 4 | |
| 0.10.1 | 8 / 4 | |
| 0.10.0 | 8 / 4 | |
| 0.9.0 | 8 / 4 | |
| 0.8.0 | 8 / 4 | |
| 0.7.3 | 8 / 4 | |
| 0.7.2 | 8 / 4 | |
| 0.7.1 | 8 / 4 | |
| 0.7.0 | 8 / 4 | |
| 0.6.2 | 8 / 4 | |
| 0.6.1 | 8 / 4 | |
| 0.6.0 | 8 / 4 | |
| 0.5.15 | 8 / 4 | |
| 0.5.14 | 8 / 4 | |
| 0.5.13 | 8 / 4 | |
| 0.5.12 | 8 / 4 | |
| 0.5.11 | 8 / 4 | |
| 0.5.10 | 8 / 4 | |
| 0.5.9 | 8 / 4 | |
| 0.5.8 | 8 / 4 | |
| 0.5.7 | 8 / 4 | |
| 0.5.6 | 8 / 4 | |
| 0.5.5 | 8 / 4 | |
| 0.5.4 | 8 / 4 | |
| 0.5.3 | 8 / 4 | |
| 0.5.2 | 8 / 4 | |
| 0.5.1 | 8 / 4 | |
| 0.5.0 | 8 / 4 | |
| 0.4.6 | 8 / 4 | |
| 0.4.5 | 8 / 4 | |
| 0.4.4 | 8 / 4 | |
| 0.4.3 | 8 / 4 | |
| 0.4.2 | 8 / 4 | |
| 0.4.1 | 8 / 4 | |
| 0.4.0 | 8 / 4 | |
| 0.3.0 | 8 / 4 | |
| 0.2.20 | 8 / 4 | |
| 0.2.19 | 8 / 4 | |
| 0.2.18 | 8 / 4 | |
| 0.2.17 | 8 / 4 | |
| 0.2.16 | 8 / 4 | |
| 0.2.15 | 8 / 4 | |
| 0.2.14 | 8 / 4 | |
| 0.2.13 | 8 / 4 | |
| 0.2.12 | 8 / 4 | |
| 0.2.11 | 8 / 4 | |
| 0.2.10 | 8 / 4 | |
| 0.2.9 | 8 / 4 | |
| 0.2.8 | 8 / 4 | |
| 0.2.7 | 8 / 4 | |
| 0.2.6 | 8 / 4 | |
| 0.2.5 | 8 / 4 | |
| 0.2.4 | 8 / 4 | |
| 0.2.3 | 8 / 4 | |
| 0.2.2 | 8 / 4 | |
| 0.2.1 | 8 / 4 | |
| 0.2.0 | 8 / 4 | |
| 0.1.5 | 8 / 4 | |
| 0.1.4 | 8 / 4 | |
| 0.1.3 | 8 / 4 | |
| 0.1.2 | 8 / 4 | |
| 0.1.1 | 8 / 4 | |
| 0.1.0 | 8 / 4 |
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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.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.5
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.4
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.3
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.