@nestjs/schematics
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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 11.1.0 | 5 / 25 | |
| 11.0.10 | 5 / 25 | |
| 11.0.9 | 5 / 25 | |
| 11.0.8 | 5 / 25 | |
| 11.0.7 | 5 / 25 | |
| 11.0.6 | 5 / 25 | |
| 11.0.5 | 5 / 25 | |
| 11.0.4 | 5 / 25 | |
| 11.0.3 | 5 / 25 | |
| 11.0.2 | 5 / 25 | |
| 11.0.1 | 5 / 25 | |
| 11.0.0 | 5 / 25 |
v11.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.