@lage-run/reporters
Log reporters 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:@lage-run/format-hrtime | AI (dependencies): Sibling package within the same @lage-run Microsoft monorepo; consistent publisher and namespace, no independent risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package; lack of Sigstore provenance is common and not a meaningful risk signal for this well-known publisher. | ai | |
| dependencies | unvetted-dep:@lage-run/logger | AI (dependencies): First-party sibling package in the microsoft/lage monorepo; same publisher and trust chain as this package. | ai | |
| dependencies | unvetted-dep:@lage-run/target-graph | AI (dependencies): First-party sibling package in the microsoft/lage monorepo; same publisher and trust chain as this package. | ai | |
| dependencies | unvetted-dep:@lage-run/scheduler-types | AI (dependencies): First-party sibling package in the microsoft/lage monorepo; same publisher and trust chain as this package. | ai | |
| dependencies | unvetted-dep:@ms-cloudpack/task-reporter | AI (dependencies): Microsoft-owned @ms-cloudpack scoped package; consistent with the lage project's organizational ownership. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 6 / 2 | |
| 1.7.5 | 6 / 2 | |
| 1.7.1 | 6 / 2 | |
| 1.7.0 | 6 / 2 | |
| 1.6.0 | 7 / 3 | |
| 1.5.1 | 8 / 3 | |
| 1.3.8 | 8 / 2 | |
| 1.3.7 | 8 / 2 |
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.