@lerna/query-graph — Greenflagged

An internal Lerna tool

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jameshenrynrwlowner

Keywords

lernautils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Lerna stewardship publicly transferred to Nrwl/Nx (jameshenry, nrwlowner) in 2022; legitimate and well-documented transition.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from evocateur to jameshenry reflects the documented Lerna → Nrwl/Nx stewardship transfer.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): jameshenry and nrwlowner are the expected new Lerna maintainers after the Nrwl/Nx transfer.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of hzoo and evocateur is consistent with the completed stewardship transfer to Nrwl/Nx.	ai	2026/04/24

Versions (showing 38 of 38)

Version	Deps	Published
6.4.1	1 / 0	2023-01-12
6.4.0	1 / 0	2023-01-05
6.3.0	1 / 0	2022-12-26
6.2.0	1 / 0	2022-12-13
6.1.0	1 / 0	2022-11-29
6.0.3	1 / 0	2022-11-07
6.0.2	1 / 0	2022-11-02
6.0.1	1 / 0	2022-10-14
6.0.0	1 / 0	2022-10-12
5.6.2	1 / 0	2022-10-09
5.6.1	1 / 0	2022-09-30
5.6.0	1 / 0	2022-09-29
5.5.4	1 / 0	2022-09-28
5.5.3	1 / 0	2022-09-28
5.5.2	1 / 0	2022-09-20
5.5.1	1 / 0	2022-09-09
5.5.0	1 / 0	2022-08-31
5.4.3	1 / 0	2022-08-16
5.4.2	1 / 0	2022-08-14
5.4.1	1 / 0	2022-08-12
5.4.0	1 / 0	2022-08-08
5.3.0	1 / 0	2022-07-27
5.2.0	1 / 0	2022-07-22
5.1.8	1 / 0	2022-07-07
5.1.7	1 / 0	2022-07-06
5.1.6	1 / 0	2022-06-24
5.1.5	1 / 0	2022-06-24
5.1.4	1 / 0	2022-06-15
5.1.3	1 / 0	2022-06-15
5.1.2	1 / 0	2022-06-13
5.1.1	1 / 0	2022-06-09
5.1.0	1 / 0	2022-06-07
5.0.0	1 / 0	2022-05-24
4.0.0	1 / 0	2021-02-10
3.18.5	2 / 0	2019-11-20
3.18.0	2 / 0	2019-10-15
3.16.0	2 / 0	2019-07-18
3.14.0	2 / 0	2019-05-14

v6.4.1

1 finding

LOW No provenance attestation provenance

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

v6.4.0

1 finding

LOW No provenance attestation provenance

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

v6.3.0

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.3

1 finding

LOW No provenance attestation provenance

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

v6.0.2

1 finding

LOW No provenance attestation provenance

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

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.6.2

1 finding

LOW No provenance attestation provenance

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

v5.6.1

1 finding

LOW No provenance attestation provenance

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

v5.6.0

1 finding

LOW No provenance attestation provenance

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

v5.5.4

1 finding

LOW No provenance attestation provenance

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

v5.5.3

1 finding

LOW No provenance attestation provenance

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

v5.5.2

1 finding

LOW No provenance attestation provenance

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

v5.5.1

1 finding

LOW No provenance attestation provenance

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

v5.5.0

1 finding

LOW No provenance attestation provenance

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

v5.4.3

1 finding

LOW No provenance attestation provenance

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

v5.4.2

1 finding

LOW No provenance attestation provenance

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

v5.4.1

1 finding

LOW No provenance attestation provenance

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

v5.4.0

1 finding

LOW No provenance attestation provenance

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

v5.3.0

1 finding

LOW No provenance attestation provenance

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

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.8

1 finding

LOW No provenance attestation provenance

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

v5.1.7

1 finding

LOW No provenance attestation provenance

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

v5.1.6

1 finding

LOW No provenance attestation provenance

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

v5.1.5

1 finding

LOW No provenance attestation provenance

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

v5.1.4

1 finding

LOW No provenance attestation provenance

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

v5.1.3

1 finding

LOW No provenance attestation provenance

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

v5.1.2

1 finding

LOW No provenance attestation provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.1.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (hzoo, evocateur) were replaced by new maintainers (jameshenry, nrwlowner). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: evocateur → jameshenry (on 2022-06-07) provenance

This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.0.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (hzoo, evocateur) were replaced by new maintainers (jameshenry, nrwlowner). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: evocateur → jameshenry (on 2022-05-24) provenance

This version was published by a different npm account than previous versions on 2022-05-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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