@lage-run/target-graph
Target for Lage
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:mergician | AI (dependencies): mergician is a legitimate object-merging utility; its use in a Microsoft build tool package is expected and low-risk. | ai | |
| dependencies | unvetted-dep:workspace-tools | AI (dependencies): workspace-tools is a Microsoft-maintained monorepo utility, consistent with this package's ecosystem and publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.6 | 3 / 2 | |
| 0.15.5 | 3 / 2 | |
| 0.14.2 | 3 / 2 | |
| 0.14.0 | 3 / 2 | |
| 0.12.3 | 3 / 2 | |
| 0.12.1 | 3 / 2 | |
| 0.12.0 | 3 / 2 | |
| 0.11.3 | 2 / 2 |
v0.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.