@ledgerhq/ledger-trust-service
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
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.8.7 | 2 / 11 | |
| 0.8.6 | 2 / 11 | |
| 0.8.5 | 2 / 11 | |
| 0.8.4 | 2 / 11 | |
| 0.8.3 | 2 / 11 | |
| 0.8.2 | 2 / 11 | |
| 0.8.1 | 2 / 11 | |
| 0.8.0 | 2 / 11 | |
| 0.7.4 | 2 / 9 | |
| 0.7.3 | 2 / 9 | |
| 0.7.2 | 2 / 9 | |
| 0.7.1 | 2 / 9 | |
| 0.7.0 | 2 / 9 | |
| 0.6.4 | 2 / 9 | |
| 0.6.3 | 2 / 9 | |
| 0.6.2 | 2 / 9 | |
| 0.6.1 | 2 / 9 | |
| 0.6.0 | 2 / 9 | |
| 0.5.0 | 2 / 8 | |
| 0.4.5 | 2 / 8 | |
| 0.4.4 | 2 / 8 | |
| 0.4.3 | 2 / 8 | |
| 0.4.2 | 2 / 8 | |
| 0.4.1 | 2 / 8 | |
| 0.4.0 | 2 / 8 | |
| 0.3.14 | 2 / 8 | |
| 0.3.13 | 2 / 8 | |
| 0.3.12 | 2 / 8 | |
| 0.3.11 | 2 / 8 | |
| 0.3.10 | 2 / 8 | |
| 0.3.9 | 2 / 8 | |
| 0.3.8 | 2 / 8 | |
| 0.3.7 | 2 / 8 | |
| 0.3.6 | 2 / 8 | |
| 0.3.5 | 2 / 8 | |
| 0.3.4 | 2 / 8 | |
| 0.3.3 | 2 / 8 | |
| 0.3.2 | 2 / 8 | |
| 0.3.1 | 2 / 8 | |
| 0.3.0 | 2 / 8 | |
| 0.2.0 | 2 / 8 | |
| 0.1.1 | 2 / 8 | |
| 0.1.0 | 2 / 8 | |
| 0.0.1 | 2 / 8 |
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.