@lage-run/config
Config management 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing for a Microsoft-owned repo; SLSA attestation confirms integrity. | ai | |
| dependencies | unvetted-dep:backfill-config | AI (dependencies): backfill-config is a known Microsoft-ecosystem build caching tool; unvetted status reflects review pipeline gap, not malicious risk. | ai | |
| dependencies | unvetted-dep:workspace-tools | AI (dependencies): workspace-tools is a well-known monorepo utility used broadly in the Microsoft JS ecosystem; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@lage-run/logger | AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/runners | AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/target-graph | AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 6 / 1 | |
| 0.9.9 | 6 / 1 | |
| 0.9.8 | 6 / 1 | |
| 0.9.7 | 6 / 1 | |
| 0.9.6 | 6 / 1 | |
| 0.9.5 | 6 / 1 | |
| 0.9.4 | 6 / 1 | |
| 0.9.3 | 6 / 1 | |
| 0.9.2 | 6 / 1 | |
| 0.9.1 | 6 / 1 | |
| 0.9.0 | 6 / 1 | |
| 0.8.0 | 6 / 1 | |
| 0.7.3 | 6 / 1 | |
| 0.7.2 | 6 / 1 | |
| 0.7.1 | 6 / 1 | |
| 0.7.0 | 6 / 1 | |
| 0.6.0 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.17 | 6 / 1 | |
| 0.4.16 | 6 / 1 | |
| 0.4.15 | 6 / 1 | |
| 0.4.14 | 6 / 1 |
v0.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.8
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.9.7
2 findingsThis version was published by a different npm account than previous versions on 2026-04-16. 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.9.6
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.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.