@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 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.36.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.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.31.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.31.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.31.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.31.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.