@kumori/kumori-module-generator
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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 3 / 7 | |
| 1.1.5 | 3 / 7 | |
| 1.1.4 | 3 / 7 | |
| 1.1.3 | 3 / 7 | |
| 1.1.2 | 3 / 7 | |
| 1.1.1 | 3 / 7 | |
| 1.1.0 | 3 / 7 | |
| 1.0.13 | 3 / 7 | |
| 1.0.12 | 3 / 7 | |
| 1.0.11 | 3 / 7 | |
| 1.0.10 | 3 / 7 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.