yeoman-generator
Rails-inspired generator system that provides scaffolding for your apps
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): @types packages are type-only and shipped as runtime deps in this TS project; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): Same as above — @types/lodash-es is a type-only dependency, stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.2.2 | 16 / 22 | |
| 8.2.1 | 16 / 22 | |
| 8.2.0 | 16 / 22 | |
| 8.1.1 | 16 / 23 | |
| 8.1.0 | 16 / 23 | |
| 8.0.2 | 16 / 23 | |
| 8.0.1 | 16 / 23 | |
| 8.0.0 | 16 / 23 |
v8.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.