@npmcli/arborist — Greenflagged

Manage node_modules trees

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

saquibkhannpm-cli-opsreggiowlstronaut

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from lukekarrys to gar reflects normal maintainer rotation within npm Inc.; both are known npm organization members with strong track records.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Trusted npm org publisher; missing gitHead is a CI environment artifact, not a supply chain indicator for this well-established package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Best-practice gap only; @npmcli/arborist is a core npm CLI package published by a trusted org maintainer with a long track record.	ai	2026/04/24
phantom-deps	phantom-dep:json-parse-even-better-errors	AI (phantom-deps): Package is declared in dependencies; not directly imported in all code paths is a false positive for this type of utility dep.	ai	2026/04/24
phantom-deps	phantom-dep:hosted-git-info	AI (phantom-deps): hosted-git-info is a declared runtime dependency in package.json; phantom-dep fires because it's referenced in config rather than directly imported in JS, not a real risk.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in bin/index.js is a standard CLI command-loader pattern iterating over known local files; not arbitrary code execution.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): gar (Gar Adams) was a former npm team member; removal reflects routine team changes at GitHub Inc., not a hostile takeover. Package is officially maintained by GitHub Inc.	ai	2026/04/23

Versions (showing 100 of 193)

Version	Deps	Published
9.7.0	34 / 9	2026-05-27
9.6.0	34 / 9	2026-05-20
9.5.0	34 / 9	2026-05-06
9.4.3	34 / 9	2026-04-22
9.4.2	34 / 9	2026-03-18
9.4.1	34 / 9	2026-03-11
9.4.0	33 / 9	2026-02-25
9.3.1	33 / 9	2026-02-19
9.3.0	33 / 9	2026-02-11
9.2.0	33 / 9	2026-02-04
9.1.10	33 / 9	2026-01-21
9.1.9	33 / 9	2025-12-09
9.1.8	33 / 9	2025-11-25
9.1.7	33 / 9	2025-11-19
9.1.6	33 / 9	2025-10-08
9.1.5	33 / 9	2025-09-24
9.1.4	34 / 9	2025-09-03
9.1.3	34 / 9	2025-07-24
9.1.2	34 / 9	2025-06-12
9.1.1	34 / 9	2025-05-21
9.1.0	34 / 9	2025-05-15
9.0.2	34 / 9	2025-04-08
9.0.1	34 / 9	2025-03-05
9.0.0	34 / 9	2024-12-16
8.0.5	36 / 8	2026-03-27
8.0.4	36 / 8	2026-03-18
8.0.3	36 / 8	2026-03-11
8.0.2	36 / 8	2026-03-04
8.0.1	35 / 8	2025-06-25
8.0.0	35 / 8	2024-10-03
7.5.4	35 / 8	2024-07-10
7.5.3	35 / 8	2024-05-29
7.5.2	35 / 8	2024-05-15
7.5.1	34 / 8	2024-04-30
7.5.0	34 / 8	2024-04-25
7.4.2	34 / 8	2024-04-10
7.4.1	33 / 8	2024-04-03
7.4.0	33 / 8	2024-02-28
7.3.1	33 / 8	2024-01-24
7.3.0	33 / 8	2024-01-10
7.2.2	33 / 8	2023-12-06
7.2.1	33 / 8	2023-10-31
7.2.0	33 / 8	2023-10-03
7.1.0	33 / 8	2023-09-08
7.0.0	33 / 8	2023-08-31
6.5.1	33 / 8	2024-02-28
6.5.0	33 / 8	2023-10-06
6.4.0	33 / 8	2023-09-18
6.3.0	33 / 8	2023-07-05
6.2.10	33 / 8	2023-06-21
6.2.9	33 / 9	2023-05-03
6.2.8	33 / 9	2023-04-19
6.2.7	33 / 9	2023-04-05
6.2.6	33 / 9	2023-03-30
6.2.5	33 / 9	2023-03-08
6.2.4	33 / 9	2023-03-02
6.2.3	33 / 9	2023-02-22
6.2.2	33 / 9	2023-02-07
6.2.1	33 / 9	2023-02-02
6.2.0	33 / 9	2023-01-25
6.1.6	33 / 8	2023-01-12
6.1.5	33 / 8	2022-12-07
6.1.4	33 / 8	2022-11-30
6.1.3	33 / 8	2022-11-16
6.1.2	33 / 8	2022-11-09
6.1.1	34 / 8	2022-11-02
6.1.0	33 / 8	2022-10-26
6.0.0	33 / 8	2022-10-19
5.6.3	37 / 8	2022-11-03
5.6.2	36 / 8	2022-09-13
5.6.1	36 / 8	2022-08-31
5.6.0	36 / 8	2022-08-17
5.5.0	36 / 8	2022-08-10
5.4.0	36 / 8	2022-08-03
5.3.1	34 / 8	2022-07-27
5.3.0	34 / 8	2022-07-12
5.2.3	34 / 8	2022-06-23
5.2.2	34 / 8	2022-06-22
5.2.1	34 / 8	2022-06-01
5.2.0	34 / 8	2022-05-11
5.1.1	34 / 8	2022-04-26
5.1.0	34 / 8	2022-04-20
5.0.6	34 / 8	2022-04-13
5.0.5	34 / 8	2022-04-07
5.0.4	34 / 8	2022-03-31
5.0.3	34 / 7	2022-03-17
5.0.2	34 / 7	2022-03-10
5.0.1	34 / 7	2022-03-08
5.0.0	34 / 7	2022-02-24
4.3.1	32 / 7	2022-02-07
4.3.0	32 / 7	2022-01-27
4.2.1	32 / 7	2022-01-20
4.2.0	32 / 7	2022-01-06
4.1.2	32 / 7	2022-01-05
4.1.1	32 / 7	2021-12-08
4.1.0	32 / 7	2021-12-02
4.0.5	32 / 6	2021-11-18
4.0.4	32 / 6	2021-11-03
4.0.3	32 / 6	2021-10-28
4.0.2	32 / 6	2021-10-20

Showing 100 of 193 Next page →

v9.7.0

1 finding

INFO No provenance attestation provenance

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

v9.6.0

1 finding

INFO No provenance attestation provenance

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

v9.5.0

1 finding

INFO No provenance attestation provenance

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

v9.4.3

1 finding

LOW No provenance attestation provenance

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

v9.4.2

2 findings

HIGH Publisher changed: gar → owlstronaut (on 2026-03-18) provenance

This version was published by a different npm account than previous versions on 2026-03-18. 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.

v9.4.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v9.4.0

2 findings

HIGH Publisher changed: reggi → owlstronaut (on 2026-02-25) provenance

This version was published by a different npm account than previous versions on 2026-02-25. 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.

v9.3.1

2 findings

HIGH Publisher changed: reggi → owlstronaut (on 2026-02-19) provenance

This version was published by a different npm account than previous versions on 2026-02-19. 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.

v9.3.0

2 findings

HIGH Publisher changed: gar → reggi (on 2026-02-11) provenance

This version was published by a different npm account than previous versions on 2026-02-11. 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.

v9.2.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2026-02-04) provenance

This version was published by a different npm account than previous versions on 2026-02-04. 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.

v9.1.10

1 finding

LOW No provenance attestation provenance

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

v9.1.9

1 finding

LOW No provenance attestation provenance

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

v9.1.8

1 finding

LOW No provenance attestation provenance

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

v9.1.7

1 finding

LOW No provenance attestation provenance

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

v9.1.6

1 finding

LOW No provenance attestation provenance

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

v9.1.5

1 finding

LOW No provenance attestation provenance

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

v9.1.4

2 findings

HIGH Publisher changed: reggi → owlstronaut (on 2025-09-03) provenance

This version was published by a different npm account than previous versions on 2025-09-03. 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.

v9.1.3

2 findings

HIGH Publisher changed: gar → reggi (on 2025-07-24) provenance

This version was published by a different npm account than previous versions on 2025-07-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.

v9.1.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v9.1.1

2 findings

HIGH Publisher changed: gar → owlstronaut (on 2025-05-21) provenance

This version was published by a different npm account than previous versions on 2025-05-21. 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.

v9.1.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: owlstronaut → gar (on 2025-05-15) provenance

This version was published by a different npm account than previous versions on 2025-05-15. 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.

v9.0.2

2 findings

HIGH Publisher changed: gar → owlstronaut (on 2025-04-08) provenance

This version was published by a different npm account than previous versions on 2025-04-08. 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.

v9.0.1

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v9.0.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v8.0.5

1 finding

LOW No provenance attestation provenance

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

v8.0.4

1 finding

LOW No provenance attestation provenance

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

v8.0.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

LOW No provenance attestation provenance

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

v8.0.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

HIGH Publisher changed: reggi → gar (on 2026-03-04) provenance

This version was published by a different npm account than previous versions on 2026-03-04. 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.

v8.0.1

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v8.0.0

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v7.5.4

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v7.5.3

3 findings

HIGH Publisher changed: lukekarrys → gar (on 2024-05-29) provenance

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

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v7.5.2

2 findings

HIGH Publisher changed: gar → lukekarrys (on 2024-05-15) provenance

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

INFO No provenance attestation provenance

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

v7.5.1

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.

v7.5.0

2 findings

INFO No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.