@lerna/package — Greenflagged

Lerna's internal representation of a package

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

lernacore

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's transfer from hzoo/evocateur to Nrwl (jameshenry/nrwlowner) in 2022 was a well-publicized, legitimate stewardship handoff, not a hijack.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change reflects the documented Lerna → Nrwl transfer; jameshenry is a long-standing npm publisher with a clean track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers jameshenry and nrwlowner are Nrwl employees who took over Lerna in a publicly announced transition.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of hzoo and evocateur is consistent with the known Lerna ownership transfer to Nrwl.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in May 2022 before Sigstore provenance was standard practice; no malicious indicators present.	ai	2026/04/24

Versions (showing 41 of 41)

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

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

1 finding

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.