@lage-run/cli
Command Line Interface 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 | no-provenance | AI (provenance): Provenance attestation is not yet standard practice; absence is not a security disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@lage-run/globby | AI (dependencies): First-party sibling package in the @lage-run Microsoft monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/logger | AI (dependencies): First-party sibling package in the @lage-run Microsoft monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/format-hrtime | AI (dependencies): First-party sibling package in the @lage-run Microsoft monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/worker-threads-pool | AI (dependencies): First-party sibling package in the @lage-run Microsoft monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| dependencies | unvetted-dep:@lage-run/rpc | AI (dependencies): First-party sibling package in the @lage-run Microsoft monorepo; unvetted status is a pipeline artifact, not a security concern. | ai | |
| phantom-deps | phantom-dep:@lage-run/scheduler-types | AI (phantom-deps): Sibling package in the same org scope; phantom dep is a minor packaging concern, not a security issue. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; documentation lives on the main project site. README quality signals are not indicative of spam or malicious intent for this well-established package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lage-run/cli is a Microsoft monorepo build tool with 1341 days of history; levenshtein match against 'joi' is a clear false positive with no impersonation intent. | ai |
Versions (showing 100 of 124)
| Version | Deps | Published |
|---|---|---|
| 0.36.12 | 20 / 4 | |
| 0.36.11 | 20 / 4 | |
| 0.36.10 | 20 / 4 | |
| 0.36.9 | 20 / 4 | |
| 0.36.8 | 20 / 4 | |
| 0.36.7 | 20 / 4 | |
| 0.36.6 | 20 / 4 | |
| 0.36.5 | 20 / 4 | |
| 0.36.4 | 20 / 4 | |
| 0.36.3 | 20 / 4 | |
| 0.36.2 | 20 / 4 | |
| 0.36.1 | 20 / 4 | |
| 0.36.0 | 20 / 4 | |
| 0.35.2 | 21 / 4 | |
| 0.35.1 | 21 / 4 | |
| 0.35.0 | 21 / 4 | |
| 0.34.1 | 21 / 4 | |
| 0.34.0 | 21 / 4 | |
| 0.33.4 | 21 / 4 | |
| 0.33.3 | 21 / 4 | |
| 0.33.2 | 21 / 4 | |
| 0.33.1 | 21 / 4 | |
| 0.33.0 | 20 / 4 | |
| 0.32.3 | 20 / 4 | |
| 0.32.2 | 20 / 4 | |
| 0.32.1 | 20 / 4 | |
| 0.32.0 | 20 / 4 | |
| 0.31.9 | 20 / 4 | |
| 0.31.8 | 20 / 4 | |
| 0.31.7 | 20 / 4 | |
| 0.31.6 | 20 / 4 | |
| 0.31.5 | 20 / 4 | |
| 0.31.4 | 20 / 4 | |
| 0.31.3 | 20 / 4 | |
| 0.31.2 | 20 / 4 | |
| 0.31.1 | 20 / 4 | |
| 0.31.0 | 20 / 4 | |
| 0.30.0 | 20 / 4 | |
| 0.29.0 | 20 / 4 | |
| 0.28.1 | 20 / 4 | |
| 0.28.0 | 20 / 4 | |
| 0.27.0 | 20 / 4 | |
| 0.26.0 | 20 / 4 | |
| 0.25.7 | 20 / 4 | |
| 0.25.6 | 20 / 4 | |
| 0.25.5 | 20 / 4 | |
| 0.25.4 | 20 / 4 | |
| 0.25.3 | 20 / 4 | |
| 0.25.2 | 20 / 4 | |
| 0.25.1 | 20 / 4 | |
| 0.25.0 | 20 / 4 | |
| 0.24.13 | 20 / 4 | |
| 0.24.12 | 20 / 4 | |
| 0.24.11 | 20 / 4 | |
| 0.24.10 | 20 / 4 | |
| 0.24.9 | 20 / 4 | |
| 0.24.8 | 20 / 4 | |
| 0.24.7 | 20 / 4 | |
| 0.24.6 | 20 / 4 | |
| 0.24.5 | 20 / 4 | |
| 0.24.4 | 19 / 4 | |
| 0.24.3 | 19 / 4 | |
| 0.24.2 | 19 / 4 | |
| 0.24.1 | 19 / 4 | |
| 0.24.0 | 19 / 4 | |
| 0.23.11 | 19 / 4 | |
| 0.23.10 | 19 / 4 | |
| 0.23.9 | 18 / 3 | |
| 0.23.8 | 18 / 3 | |
| 0.23.7 | 18 / 3 | |
| 0.23.6 | 18 / 3 | |
| 0.23.5 | 18 / 3 | |
| 0.23.4 | 18 / 3 | |
| 0.23.3 | 17 / 2 | |
| 0.23.2 | 17 / 2 | |
| 0.23.1 | 17 / 2 | |
| 0.23.0 | 17 / 2 | |
| 0.22.0 | 17 / 2 | |
| 0.21.0 | 16 / 2 | |
| 0.20.0 | 16 / 2 | |
| 0.19.3 | 16 / 2 | |
| 0.19.2 | 16 / 2 | |
| 0.19.1 | 16 / 2 | |
| 0.19.0 | 15 / 2 | |
| 0.18.1 | 14 / 2 | |
| 0.18.0 | 14 / 2 | |
| 0.17.8 | 14 / 2 | |
| 0.17.7 | 13 / 2 | |
| 0.17.6 | 13 / 2 | |
| 0.17.5 | 13 / 2 | |
| 0.17.4 | 13 / 2 | |
| 0.17.3 | 13 / 2 | |
| 0.17.2 | 13 / 2 | |
| 0.17.1 | 13 / 2 | |
| 0.17.0 | 13 / 2 | |
| 0.3.19 | 7 / 1 | |
| 0.3.18 | 7 / 1 | |
| 0.3.17 | 7 / 1 | |
| 0.3.16 | 7 / 1 | |
| 0.3.15 | 7 / 1 |
v0.36.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.3
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.
v0.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
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 (kenotron_msft) than the most recent previously approved version (ecraig12345_msft) on 2024-06-18, but kenotron_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.
v0.17.3
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 (kenotron_msft) than the most recent previously approved version (ecraig12345_msft) on 2024-06-10, but kenotron_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.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.