npm-package-arg
Parse the things that can be arguments to `npm install`
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): npm CLI team packages do not consistently use Sigstore provenance; absence is a process gap, not a security risk for this trusted package. | ai | |
| provenance | missing-githead | AI (provenance): Established npm-org package; missing gitHead is a publish-environment hygiene issue, not a security signal for this well-known package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (npm-cli-ops, fritzy, saquibkhan, reggi, hashtagchris) are known npm CLI team members; this reflects organizational consolidation, not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): proc-log is an official npm CLI team package used for logging; not a suspicious dependency for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers (isaacs, darcyclarke, ruyadorno, nlf) reflect npm team reorganization; consistent with known npm CLI team transitions. | ai | |
| provenance | publisher-changed | AI (provenance): npm-cli-ops is the npm CLI team's official bot account; publisher transitions to this account are expected for npm's own tooling packages and are backed by SLSA provenance. | ai | |
| dependencies | unvetted-dep:validate-npm-package-name | AI (dependencies): validate-npm-package-name is an official npm-org package and a well-known legitimate dependency; the unvetted flag is a pipeline gap, not a real risk. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 14.0.0 | 4 / 3 | |
| 13.0.2 | 4 / 3 | |
| 13.0.1 | 4 / 3 | |
| 13.0.0 | 4 / 3 | |
| 12.0.2 | 4 / 3 | |
| 12.0.1 | 4 / 3 | |
| 12.0.0 | 4 / 3 | |
| 11.0.3 | 4 / 3 | |
| 11.0.2 | 4 / 3 | |
| 11.0.1 | 4 / 3 | |
| 11.0.0 | 4 / 3 | |
| 10.1.0 | 4 / 3 | |
| 10.0.0 | 4 / 3 | |
| 9.1.2 | 4 / 3 | |
| 9.1.1 | 4 / 3 | |
| 9.1.0 | 4 / 3 | |
| 9.0.2 | 3 / 3 | |
| 9.0.1 | 3 / 2 | |
| 9.0.0 | 3 / 2 | |
| 8.1.5 | 3 / 2 | |
| 8.1.4 | 3 / 2 | |
| 8.1.3 | 3 / 2 | |
| 8.1.2 | 3 / 1 | |
| 8.1.1 | 3 / 1 | |
| 8.1.0 | 3 / 1 | |
| 8.0.1 | 3 / 1 | |
| 8.0.0 | 4 / 3 | |
| 7.0.0 | 4 / 5 | |
| 6.1.1 | 4 / 5 | |
| 6.1.0 | 4 / 5 | |
| 6.0.0 | 4 / 2 | |
| 5.1.2 | 4 / 2 | |
| 5.1.1 | 4 / 2 | |
| 5.1.0 | 4 / 2 | |
| 5.0.1 | 4 / 2 | |
| 5.0.0 | 4 / 2 | |
| 4.2.1 | 2 / 2 | |
| 4.2.0 | 2 / 2 | |
| 4.1.1 | 2 / 1 | |
| 4.1.0 | 2 / 1 | |
| 4.0.2 | 2 / 1 | |
| 4.0.1 | 2 / 1 | |
| 4.0.0 | 2 / 1 | |
| 3.1.1 | 2 / 1 | |
| 3.1.0 | 2 / 1 | |
| 3.0.0 | 2 / 1 | |
| 2.1.3 | 1 / 1 | |
| 2.1.2 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 | |
| 2.0.4 | 1 / 1 | |
| 2.0.3 | 1 / 1 | |
| 2.0.2 | 1 / 1 | |
| 2.0.1 | 1 / 1 | |
| 2.0.0 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v14.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.2
2 findingsThis version was published by a different npm account than previous versions on 2025-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.1
2 findingsThis version was published by a different npm account than previous versions on 2024-12-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-09-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-07-22. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-05. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-15. This could indicate a legitimate maintainer transition or an account compromise.
v10.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-01. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-18. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-28. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-28. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-22. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-15. This could indicate a legitimate maintainer transition or an account compromise.
v9.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-10. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-18. This could indicate a legitimate maintainer transition or an account compromise.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-13. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-12. This could indicate a legitimate maintainer transition or an account compromise.
v8.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-11. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-21. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-10. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-18. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-08. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-06-02. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-04-14. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v4.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-15. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-19. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-07-16. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-05-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-04-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-10-28. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-29. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-05. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.