← Home

@lage-run/scheduler-types

npm Repository Homepage

Scheduler types for Lage

53
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 from personal Microsoft employee account to GitHub Actions CI/CD is intentional and backed by SLSA provenance attestation from the microsoft/lage repo. Stable for this package going forward. ai
dependencies unvetted-dep:@lage-run/target-graph AI (dependencies): @lage-run/target-graph is a sibling package in the same Microsoft lage monorepo — a trusted intra-monorepo dependency, not a third-party risk. ai

Versions (showing 53 of 53)

Version Deps Published
0.4.11 1 / 1
0.4.10 1 / 1
0.4.9 1 / 1
0.4.8 1 / 1
0.4.7 1 / 1
0.4.6 1 / 1
0.4.5 1 / 1
0.4.4 1 / 1
0.4.3 1 / 1
0.4.2 1 / 1
0.4.1 1 / 1
0.4.0 1 / 1
0.3.32 1 / 1
0.3.31 1 / 1
0.3.30 1 / 1
0.3.29 1 / 1
0.3.28 1 / 1
0.3.27 1 / 1
0.3.26 1 / 1
0.3.25 1 / 1
0.3.24 1 / 1
0.3.23 1 / 1
0.3.22 1 / 1
0.3.21 1 / 1
0.3.20 1 / 1
0.3.19 1 / 1
0.3.18 1 / 1
0.3.17 1 / 1
0.3.16 1 / 1
0.3.15 1 / 1
0.3.14 1 / 1
0.3.13 1 / 1
0.3.12 1 / 1
0.3.11 1 / 1
0.3.10 1 / 1
0.3.9 1 / 1
0.3.8 1 / 1
0.3.7 1 / 1
0.3.6 1 / 1
0.3.5 1 / 1
0.3.4 1 / 1
0.3.3 1 / 1
0.3.2 1 / 1
0.3.1 1 / 1
0.3.0 1 / 1
0.2.10 1 / 1
0.2.9 1 / 1
0.2.8 1 / 1
0.2.7 1 / 1
0.2.6 1 / 1
0.2.5 2 / 1
0.2.4 2 / 1
0.2.3 2 / 1

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

v0.3.24

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

1 finding
LOW No provenance attestation provenance

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

v0.3.22

1 finding
LOW No provenance attestation provenance

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

v0.3.21

1 finding
LOW No provenance attestation provenance

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

v0.3.20

1 finding
LOW No provenance attestation provenance

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

v0.3.19

1 finding
LOW No provenance attestation provenance

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

v0.3.18

1 finding
LOW No provenance attestation provenance

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

v0.3.17

1 finding
LOW No provenance attestation provenance

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

v0.3.16

1 finding
LOW No provenance attestation provenance

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

v0.3.15

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

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

1 finding
LOW No provenance attestation provenance

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

v0.3.12

1 finding
LOW No provenance attestation provenance

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

v0.3.11

1 finding
LOW No provenance attestation provenance

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

v0.3.10

1 finding
LOW No provenance attestation provenance

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

v0.3.9

1 finding
LOW No provenance attestation provenance

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

v0.3.8

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

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

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

2 findings
MEDIUM Publisher changed: kenotron_msft → ecraig12345_msft (on 2023-03-08, unremoved on npm for 1231d) provenance

This version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2023-03-08. It has since remained available on npm for 1231 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

1 finding
LOW No provenance attestation provenance

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

v0.2.9

1 finding
LOW No provenance attestation provenance

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

v0.2.8

1 finding
LOW No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

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.