@openapi-generator-plus/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 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.22.2 | 0 / 2 | |
| 2.22.1 | 0 / 2 | |
| 2.22.0 | 0 / 2 | |
| 2.21.0 | 0 / 2 | |
| 2.20.0 | 0 / 2 | |
| 2.19.0 | 0 / 2 | |
| 2.18.0 | 0 / 2 | |
| 2.17.0 | 0 / 2 | |
| 2.16.0 | 0 / 2 | |
| 2.15.0 | 0 / 2 | |
| 2.14.0 | 0 / 2 |
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.