yeoman-environment
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:yeoman-environment | AI (npm-metadata): Self-referencing file:./ in devDependencies is a documented self-test pattern for this package; stable across versions. | ai | |
| dependencies | unvetted-peer-dep:@yeoman/adapter | AI (dependencies): Internal Yeoman peer dependency; stable across versions. | ai | |
| dependencies | unvetted-dep:mem-fs-editor | AI (dependencies): Core Yeoman file-system utility; stable for this package. | ai | |
| dependencies | unvetted-dep:@yeoman/adapter | AI (dependencies): First-party @yeoman scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:fly-import | AI (dependencies): Legitimate Yeoman ecosystem utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@yeoman/conflicter | AI (dependencies): First-party @yeoman scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:which-package-manager | AI (dependencies): Small utility dep; no risk signal for this package. | ai | |
| dependencies | unvetted-dep:@yeoman/transform | AI (dependencies): First-party @yeoman scoped package; stable for this package. | ai | |
| dependencies | unvetted-dep:grouped-queue | AI (dependencies): Long-standing Yeoman ecosystem dependency; no risk signal. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 21 / 27 | |
| 6.0.1 | 21 / 27 | |
| 6.0.0 | 21 / 27 | |
| 5.1.3 | 21 / 27 | |
| 5.1.2 | 21 / 27 | |
| 5.1.1 | 21 / 27 | |
| 5.1.0 | 21 / 27 |
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.