← Home

@lage-run/scheduler

npm Repository Homepage

Scheduler for Lage

63
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): Package migrated to GitHub Actions publishing with SLSA attestation; legitimate CI/CD transition for Microsoft/lage monorepo. ai
dependencies unvetted-dep:@lage-run/config AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/hasher AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/logger AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/cache AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/target-graph AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/worker-threads-pool AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai
dependencies unvetted-dep:@lage-run/runners AI (dependencies): First-party sibling package from the same Microsoft lage monorepo; consistent namespace and SLSA provenance on parent package mitigates risk. ai

Versions (showing 63 of 63)

Version Deps Published
1.6.12 8 / 3
1.6.11 8 / 3
1.6.10 8 / 3
1.6.9 8 / 3
1.6.8 8 / 3
1.6.7 8 / 3
1.6.6 7 / 3
1.6.5 7 / 3
1.6.4 7 / 3
1.6.3 7 / 3
1.6.2 7 / 3
1.6.1 7 / 3
1.6.0 7 / 3
1.5.23 7 / 3
1.5.22 7 / 3
1.5.21 7 / 3
1.5.20 7 / 2
1.5.19 7 / 2
1.5.18 7 / 2
1.5.17 7 / 2
1.5.16 7 / 2
1.5.15 7 / 2
1.5.14 7 / 2
1.5.13 7 / 2
1.5.12 7 / 2
1.5.11 7 / 2
1.5.10 7 / 2
1.5.9 7 / 2
1.5.8 7 / 2
1.5.7 7 / 2
1.5.6 7 / 2
1.5.5 7 / 2
1.5.4 7 / 2
1.5.3 7 / 2
1.5.2 7 / 2
1.5.1 7 / 2
1.5.0 7 / 2
1.4.5 7 / 2
1.4.4 7 / 2
1.4.3 7 / 2
1.4.2 7 / 2
1.4.1 7 / 2
1.4.0 7 / 2
1.3.12 7 / 2
1.3.11 7 / 2
1.3.10 7 / 2
1.3.9 7 / 2
1.3.8 7 / 2
1.3.7 7 / 2
1.3.6 7 / 2
1.3.5 7 / 2
1.3.4 7 / 2
1.3.3 7 / 2
1.3.2 7 / 2
1.3.1 7 / 2
1.3.0 7 / 2
1.2.14 7 / 2
1.2.13 7 / 2
1.2.12 7 / 2
1.2.11 7 / 2
1.2.10 7 / 2
1.2.9 7 / 2
1.2.8 7 / 2

v1.6.12

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.

v1.6.11

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.

v1.5.5

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.

v1.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.5

1 finding
LOW No provenance attestation provenance

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.12

1 finding
LOW No provenance attestation provenance

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

v1.3.11

1 finding
LOW No provenance attestation provenance

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

v1.3.10

1 finding
LOW No provenance attestation provenance

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

v1.3.9

1 finding
LOW No provenance attestation provenance

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

v1.3.8

1 finding
LOW No provenance attestation provenance

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

v1.3.7

1 finding
LOW No provenance attestation provenance

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

v1.3.6

1 finding
LOW No provenance attestation provenance

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

v1.3.5

1 finding
LOW No provenance attestation provenance

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

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.14

1 finding
LOW No provenance attestation provenance

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

v1.2.13

1 finding
LOW No provenance attestation provenance

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

v1.2.12

1 finding
LOW No provenance attestation provenance

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

v1.2.11

1 finding
LOW No provenance attestation provenance

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

v1.2.10

1 finding
LOW No provenance attestation provenance

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

v1.2.9

1 finding
LOW No provenance attestation provenance

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

v1.2.8

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.