@statoscope/types
Statoscope types
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
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.28.1 | 1 / 0 | |
| 5.27.0 | 1 / 0 | |
| 5.22.0 | 1 / 0 | |
| 5.14.1 | 1 / 0 | |
| 5.13.1 | 1 / 0 | |
| 5.12.1 | 1 / 0 | |
| 5.9.0 | 1 / 0 | |
| 5.7.1 | 1 / 0 | |
| 5.7.0 | 1 / 0 |
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.