← Home

@lage-run/scheduler

npm Repository Homepage

Scheduler for Lage

26
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_msft

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 26 of 26)

Version Deps Published
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

v1.6.7

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

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

2 findings
HIGH Publisher changed: ecraig12345_msft → GitHub Actions (on 2026-04-25) provenance

This version was published by a different npm account than previous versions on 2026-04-25. This could indicate a legitimate maintainer transition or an account compromise.

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

2 findings
HIGH Publisher changed: ecraig12345_msft → GitHub Actions (on 2026-04-16) provenance

This version was published by a different npm account than previous versions on 2026-04-16. This could indicate a legitimate maintainer transition or an account compromise.

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

2 findings
HIGH Publisher changed: ecraig12345_msft → GitHub Actions (on 2026-04-10) provenance

This version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.

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

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.23

1 finding
LOW No provenance attestation provenance

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

v1.5.22

1 finding
LOW No provenance attestation provenance

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

v1.5.21

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.

v1.5.20

1 finding
LOW No provenance attestation provenance

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

v1.5.19

1 finding
LOW No provenance attestation provenance

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

v1.5.18

1 finding
LOW No provenance attestation provenance

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

v1.5.17

1 finding
LOW No provenance attestation provenance

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

v1.5.16

1 finding
LOW No provenance attestation provenance

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

v1.5.14

1 finding
LOW No provenance attestation provenance

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

v1.5.13

1 finding
LOW No provenance attestation provenance

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

v1.5.12

1 finding
LOW No provenance attestation provenance

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

v1.5.11

1 finding
LOW No provenance attestation provenance

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

v1.5.10

1 finding
LOW No provenance attestation provenance

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

v1.5.9

1 finding
LOW No provenance attestation provenance

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

v1.5.8

1 finding
LOW No provenance attestation provenance

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

v1.5.7

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.

v1.5.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.