← Home

@lage-run/config

npm Repository Homepage

Config management for Lage

51
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

microsoft1eskenotron_msftecraig12345_msftmicrosoft-oss-releases

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing for a Microsoft-owned repo; SLSA attestation confirms integrity. ai
dependencies unvetted-dep:backfill-config AI (dependencies): backfill-config is a known Microsoft-ecosystem build caching tool; unvetted status reflects review pipeline gap, not malicious risk. ai
dependencies unvetted-dep:workspace-tools AI (dependencies): workspace-tools is a well-known monorepo utility used broadly in the Microsoft JS ecosystem; no malicious indicators. ai
dependencies unvetted-dep:@lage-run/logger AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. ai
dependencies unvetted-dep:@lage-run/runners AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. ai
dependencies unvetted-dep:@lage-run/target-graph AI (dependencies): Sibling package within the microsoft/lage monorepo; unvetted status is a pipeline artifact, not a security concern. ai

Versions (showing 51 of 55)

View all versions
Version Deps Published
0.9.15 6 / 1
0.9.14 6 / 1
0.9.13 6 / 1
0.9.12 6 / 1
0.9.11 6 / 1
0.9.10 6 / 1
0.9.9 6 / 1
0.9.8 6 / 1
0.9.7 6 / 1
0.9.6 6 / 1
0.9.5 6 / 1
0.9.4 6 / 1
0.9.3 6 / 1
0.9.2 6 / 1
0.9.1 6 / 1
0.9.0 6 / 1
0.8.0 6 / 1
0.7.3 6 / 1
0.7.2 6 / 1
0.7.1 6 / 1
0.7.0 6 / 1
0.6.0 6 / 1
0.5.0 6 / 1
0.4.17 6 / 1
0.4.16 6 / 1
0.4.15 6 / 1
0.4.14 6 / 1
0.4.13 6 / 1
0.4.12 6 / 1
0.4.11 6 / 1
0.4.10 6 / 1
0.4.9 6 / 1
0.4.8 6 / 1
0.4.7 6 / 1
0.4.6 6 / 1
0.4.5 6 / 1
0.4.4 6 / 1
0.4.3 6 / 1
0.4.2 6 / 1
0.4.1 6 / 1
0.4.0 6 / 1
0.3.7 6 / 1
0.3.6 6 / 1
0.3.5 6 / 1
0.3.4 6 / 1
0.3.3 6 / 1
0.3.2 6 / 1
0.3.1 6 / 1
0.3.0 6 / 1
0.2.1 6 / 1
0.2.0 6 / 1

v0.9.15

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.4.13

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: kenotron_msft → ecraig12345_msft (on 2025-04-17, known maintainer) provenance

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.4.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.7

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: ecraig12345_msft → kenotron_msft (on 2024-08-28, known maintainer) provenance

This version was published by a different npm account (kenotron_msft) than the most recent previously approved version (ecraig12345_msft) on 2024-08-28, 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.3.6

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.