@npmcli/arborist
Manage node_modules trees
Supply chain provenance
Status for the latest visible version.
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
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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 51 of 193)
| Version | Deps | Published |
|---|---|---|
| 9.7.0 | 34 / 9 | |
| 9.6.0 | 34 / 9 | |
| 9.5.0 | 34 / 9 | |
| 9.4.3 | 34 / 9 | |
| 9.4.2 | 34 / 9 | |
| 9.4.1 | 34 / 9 | |
| 9.4.0 | 33 / 9 | |
| 9.3.1 | 33 / 9 | |
| 9.3.0 | 33 / 9 | |
| 9.2.0 | 33 / 9 | |
| 9.1.10 | 33 / 9 | |
| 9.1.9 | 33 / 9 | |
| 9.1.8 | 33 / 9 | |
| 9.1.7 | 33 / 9 | |
| 9.1.6 | 33 / 9 | |
| 9.1.5 | 33 / 9 | |
| 9.1.4 | 34 / 9 | |
| 9.1.3 | 34 / 9 | |
| 9.1.2 | 34 / 9 | |
| 9.1.1 | 34 / 9 | |
| 9.1.0 | 34 / 9 | |
| 9.0.2 | 34 / 9 | |
| 9.0.1 | 34 / 9 | |
| 9.0.0 | 34 / 9 | |
| 8.0.5 | 36 / 8 | |
| 8.0.4 | 36 / 8 | |
| 8.0.3 | 36 / 8 | |
| 8.0.2 | 36 / 8 | |
| 8.0.1 | 35 / 8 | |
| 8.0.0 | 35 / 8 | |
| 7.5.4 | 35 / 8 | |
| 7.5.3 | 35 / 8 | |
| 7.5.2 | 35 / 8 | |
| 7.5.1 | 34 / 8 | |
| 7.5.0 | 34 / 8 | |
| 7.4.2 | 34 / 8 | |
| 7.4.1 | 33 / 8 | |
| 7.4.0 | 33 / 8 | |
| 7.3.1 | 33 / 8 | |
| 7.3.0 | 33 / 8 | |
| 7.2.2 | 33 / 8 | |
| 7.2.1 | 33 / 8 | |
| 7.2.0 | 33 / 8 | |
| 7.1.0 | 33 / 8 | |
| 7.0.0 | 33 / 8 | |
| 6.5.1 | 33 / 8 | |
| 6.5.0 | 33 / 8 | |
| 6.4.0 | 33 / 8 | |
| 6.3.0 | 33 / 8 | |
| 6.2.10 | 33 / 8 | |
| 6.2.9 | 33 / 9 |
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.