@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 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 0.3.14 | 7 / 1 | |
| 0.3.13 | 7 / 1 | |
| 0.3.12 | 7 / 1 | |
| 0.3.11 | 7 / 1 | |
| 0.3.10 | 7 / 1 | |
| 0.3.9 | 7 / 1 | |
| 0.3.8 | 7 / 6 | |
| 0.3.7 | 7 / 6 | |
| 0.3.6 | 7 / 6 | |
| 0.3.5 | 7 / 6 | |
| 0.3.4 | 7 / 6 | |
| 0.3.3 | 7 / 6 | |
| 0.3.2 | 7 / 6 | |
| 0.3.1 | 7 / 5 | |
| 0.3.0 | 7 / 5 | |
| 0.2.4 | 7 / 5 | |
| 0.2.3 | 7 / 6 | |
| 0.2.2 | 7 / 6 | |
| 0.2.1 | 7 / 6 | |
| 0.2.0 | 7 / 6 | |
| 0.1.4 | 7 / 6 | |
| 0.1.3 | 7 / 6 | |
| 0.1.2 | 7 / 6 | |
| 0.1.1 | 7 / 6 |
v0.3.14
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.13
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.12
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.11
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.10
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.9
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.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.
v0.3.7
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.6
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.5
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.4
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.3
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.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.3.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.3.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.2.4
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.2.3
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.2.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.2.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.2.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.1.4
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.1.3
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.1.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.1.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.