keyv-file
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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.3.5 | 2 / 8 | |
| 5.3.4 | 2 / 8 | |
| 5.3.3 | 2 / 8 | |
| 5.3.2 | 2 / 8 | |
| 5.3.1 | 2 / 8 | |
| 5.3.0 | 2 / 7 | |
| 5.2.0 | 2 / 8 | |
| 5.1.5 | 2 / 8 | |
| 5.1.3 | 3 / 8 | |
| 5.1.2 | 3 / 8 | |
| 5.1.1 | 3 / 8 | |
| 5.1.0 | 3 / 8 | |
| 5.0.4 | 3 / 8 | |
| 5.0.3 | 3 / 8 | |
| 5.0.2 | 2 / 8 | |
| 5.0.1 | 2 / 8 | |
| 5.0.0 | 2 / 8 |
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.