@lage-run/target-graph MIT 55 versions

@lage-run/target-graph

npm Repository Homepage

Target for Lage

55

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:mergician	AI (dependencies): mergician is a legitimate object-merging utility; its use in a Microsoft build tool package is expected and low-risk.	ai	2026/04/25
dependencies	unvetted-dep:workspace-tools	AI (dependencies): workspace-tools is a Microsoft-maintained monorepo utility, consistent with this package's ecosystem and publisher.	ai	2026/04/25

Versions (showing 55 of 55)

Version	Deps	Published
0.15.10	3 / 2	2026-07-09
0.15.9	3 / 2	2026-06-25
0.15.8	3 / 2	2026-06-25
0.15.7	3 / 2	2026-06-12
0.15.6	3 / 2	2026-05-01
0.15.5	3 / 2	2026-04-25
0.14.2	3 / 2	2026-04-02
0.14.0	3 / 2	2026-03-19
0.12.3	3 / 2	2026-02-10
0.12.1	3 / 2	2026-01-15
0.12.0	3 / 2	2025-09-01
0.11.3	2 / 2	2025-08-01
0.11.2	2 / 2	2025-04-17
0.11.1	2 / 2	2025-01-15
0.11.0	2 / 2	2024-12-02
0.10.1	2 / 2	2024-11-20
0.10.0	2 / 2	2024-11-08
0.9.3	1 / 2	2024-10-22
0.9.2	1 / 2	2024-10-21
0.9.1	1 / 1	2024-10-17
0.9.0	1 / 1	2024-10-02
0.8.10	1 / 1	2024-09-13
0.8.9	1 / 1	2023-12-21
0.8.8	1 / 1	2023-12-12
0.8.7	1 / 1	2023-07-17
0.8.6	1 / 1	2023-05-08
0.8.5	1 / 1	2023-05-08
0.8.4	1 / 1	2023-04-25
0.8.3	1 / 1	2023-04-14
0.8.2	1 / 1	2023-04-06
0.8.1	1 / 1	2023-03-14
0.8.0	1 / 1	2023-03-10
0.7.0	1 / 1	2023-03-08
0.6.2	1 / 1	2023-02-15
0.6.1	1 / 1	2022-11-11
0.6.0	1 / 1	2022-11-10
0.5.3	1 / 1	2022-11-01
0.5.2	1 / 1	2022-11-01
0.5.1	1 / 1	2022-10-29
0.5.0	1 / 1	2022-10-26
0.4.5	1 / 1	2022-10-26
0.4.4	1 / 1	2022-10-23
0.4.3	1 / 1	2022-10-20
0.4.2	1 / 1	2022-10-03
0.4.1	1 / 1	2022-10-01
0.4.0	1 / 1	2022-10-01
0.3.5	1 / 1	2022-10-01
0.3.4	1 / 1	2022-09-29
0.3.3	1 / 3	2022-09-19
0.3.2	1 / 3	2022-09-17
0.3.1	1 / 3	2022-09-06
0.3.0	1 / 3	2022-09-04
0.2.2	1 / 3	2022-08-24
0.2.1	1 / 3	2022-08-24
0.2.0	1 / 3	2022-08-09

v0.15.10

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

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

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.10

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

1 finding

LOW No provenance attestation provenance

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

v0.8.8

1 finding

LOW No provenance attestation provenance

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

v0.8.7

1 finding

LOW No provenance attestation provenance

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

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.5

1 finding

LOW No provenance attestation provenance

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

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

2 findings

MEDIUM Publisher changed: kenotron_msft → ecraig12345_msft (on 2023-03-10, unremoved on npm for 1229d) provenance

This version was published by a different npm account (ecraig12345_msft) than the most recent previously approved version (kenotron_msft) on 2023-03-10. It has since remained available on npm for 1229 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.7.0

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

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.