@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 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.8.4 | 6 / 2 | |
| 1.8.3 | 6 / 2 | |
| 1.8.2 | 6 / 2 | |
| 1.8.1 | 6 / 2 | |
| 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.5.0 | 8 / 2 | |
| 1.4.1 | 8 / 2 | |
| 1.4.0 | 8 / 2 | |
| 1.3.8 | 8 / 2 | |
| 1.3.7 | 8 / 2 | |
| 1.3.6 | 8 / 1 | |
| 1.3.5 | 8 / 1 | |
| 1.3.4 | 8 / 1 | |
| 1.3.3 | 8 / 1 | |
| 1.3.2 | 8 / 1 | |
| 1.3.1 | 8 / 1 | |
| 1.3.0 | 8 / 1 | |
| 1.2.19 | 8 / 1 | |
| 1.2.18 | 8 / 1 | |
| 1.2.17 | 8 / 1 | |
| 1.2.16 | 8 / 1 | |
| 1.2.15 | 8 / 1 | |
| 1.2.14 | 8 / 1 | |
| 1.2.13 | 8 / 1 | |
| 1.2.12 | 8 / 1 | |
| 1.2.11 | 8 / 1 | |
| 1.2.10 | 8 / 1 | |
| 1.2.9 | 8 / 1 | |
| 1.2.8 | 8 / 1 | |
| 1.2.7 | 8 / 1 | |
| 1.2.6 | 8 / 1 | |
| 1.2.5 | 8 / 1 | |
| 1.2.4 | 8 / 1 | |
| 1.2.3 | 8 / 1 | |
| 1.2.2 | 8 / 1 | |
| 1.2.1 | 8 / 1 | |
| 1.2.0 | 8 / 1 | |
| 1.1.2 | 8 / 1 | |
| 1.1.1 | 8 / 1 | |
| 1.1.0 | 8 / 1 | |
| 1.0.7 | 9 / 2 | |
| 1.0.6 | 9 / 2 | |
| 1.0.5 | 9 / 2 | |
| 1.0.4 | 9 / 2 | |
| 1.0.3 | 9 / 2 | |
| 1.0.2 | 9 / 2 |
v1.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2025-04-17, but ecraig12345_msft is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2023-02-18. It has since remained available on npm for 1249 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.