@lage-run/grapher
Generates a list of dependents and dependencies (internal to the monorepo) for a package or packages.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Microsoft's lage monorepo migrated publishing from individual MSFT employee accounts to GitHub Actions CI/CD. SLSA provenance attestation confirms legitimate pipeline publishing; this pattern generalizes to all future versions. | ai | |
| dependencies | unvetted-dep:workspace-tools | AI (dependencies): workspace-tools is a legitimate, widely-used monorepo utility package; its use in the lage monorepo toolchain is expected and stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.26 | 2 / 1 | |
| 0.2.25 | 2 / 1 | |
| 0.2.24 | 2 / 1 | |
| 0.2.23 | 2 / 1 | |
| 0.2.22 | 2 / 1 | |
| 0.2.21 | 2 / 1 | |
| 0.2.20 | 2 / 1 |
v0.2.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.24
2 findingsThis version was published by a different npm account than previous versions on 2026-04-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.23
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.