@keyvhq/compress
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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.2.4 | 1 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.15 | 1 / 2 | |
| 2.1.14 | 1 / 2 | |
| 2.1.13 | 1 / 2 | |
| 2.1.11 | 1 / 2 | |
| 2.1.7 | 1 / 2 | |
| 2.1.5 | 1 / 2 | |
| 2.1.1 | 1 / 2 | |
| 2.0.3 | 1 / 2 | |
| 2.0.0 | 1 / 3 |
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.