@yeoman/types
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.11.1 | 0 / 4 | |
| 1.11.0 | 0 / 4 | |
| 1.10.3 | 0 / 4 | |
| 1.10.2 | 0 / 4 | |
| 1.10.1 | 0 / 4 | |
| 1.10.0 | 0 / 4 | |
| 1.9.1 | 0 / 4 | |
| 1.9.0 | 0 / 4 | |
| 1.8.0 | 0 / 4 | |
| 1.7.1 | 0 / 4 | |
| 1.7.0 | 0 / 4 |
v1.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.