libnpmexec
npm exec (npx) programmatic API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish environment variation within the npm CLI team; gitHead presence is not guaranteed across all publish flows. | ai | |
| provenance | no-provenance | AI (provenance): Informational finding; npm CLI workspace packages may not yet have Sigstore provenance enabled. Not a security risk. | ai | |
| provenance | publisher-changed | AI (provenance): reggi is a known npm CLI team member; publisher change from gar to reggi is a legitimate maintainer rotation within the npm org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @npmcli/package-json is an official @npmcli-scoped package, consistent with the existing dependency tree. | ai |
Versions (showing 100 of 101)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 12 / 8 | |
| 11.0.0 | 12 / 8 | |
| 10.3.1 | 12 / 8 | |
| 10.3.0 | 12 / 8 | |
| 10.2.9 | 12 / 8 | |
| 10.2.8 | 12 / 8 | |
| 10.2.7 | 12 / 8 | |
| 10.2.6 | 12 / 8 | |
| 10.2.5 | 12 / 8 | |
| 10.2.4 | 12 / 8 | |
| 10.2.3 | 12 / 8 | |
| 10.2.2 | 12 / 8 | |
| 10.2.1 | 12 / 8 | |
| 10.2.0 | 12 / 8 | |
| 10.1.12 | 12 / 8 | |
| 10.1.11 | 12 / 8 | |
| 10.1.10 | 12 / 8 | |
| 10.1.9 | 12 / 8 | |
| 10.1.8 | 12 / 8 | |
| 10.1.7 | 12 / 8 | |
| 10.1.6 | 11 / 8 | |
| 10.1.5 | 11 / 8 | |
| 10.1.4 | 11 / 8 | |
| 10.1.3 | 11 / 8 | |
| 10.1.2 | 11 / 8 | |
| 10.1.1 | 11 / 8 | |
| 10.1.0 | 11 / 8 | |
| 10.0.0 | 10 / 8 | |
| 9.0.5 | 10 / 8 | |
| 9.0.4 | 10 / 8 | |
| 9.0.3 | 10 / 8 | |
| 9.0.2 | 10 / 8 | |
| 9.0.1 | 10 / 8 | |
| 9.0.0 | 10 / 8 | |
| 8.1.4 | 10 / 8 | |
| 8.1.3 | 10 / 8 | |
| 8.1.2 | 10 / 8 | |
| 8.1.1 | 10 / 8 | |
| 8.1.0 | 10 / 8 | |
| 8.0.0 | 10 / 8 | |
| 7.0.10 | 11 / 8 | |
| 7.0.9 | 11 / 8 | |
| 7.0.8 | 11 / 8 | |
| 7.0.7 | 11 / 8 | |
| 7.0.6 | 11 / 8 | |
| 7.0.5 | 11 / 8 | |
| 7.0.4 | 11 / 8 | |
| 7.0.3 | 11 / 8 | |
| 7.0.2 | 11 / 8 | |
| 7.0.1 | 11 / 8 | |
| 7.0.0 | 11 / 8 | |
| 6.0.5 | 11 / 8 | |
| 6.0.4 | 11 / 8 | |
| 6.0.3 | 11 / 8 | |
| 6.0.2 | 11 / 8 | |
| 6.0.1 | 11 / 8 | |
| 6.0.0 | 11 / 9 | |
| 5.0.17 | 12 / 8 | |
| 5.0.16 | 12 / 8 | |
| 5.0.15 | 12 / 8 | |
| 5.0.14 | 12 / 8 | |
| 5.0.13 | 12 / 8 | |
| 5.0.12 | 12 / 8 | |
| 5.0.11 | 12 / 8 | |
| 5.0.10 | 12 / 8 | |
| 5.0.9 | 12 / 9 | |
| 5.0.8 | 12 / 9 | |
| 5.0.7 | 12 / 9 | |
| 5.0.6 | 12 / 9 | |
| 5.0.5 | 12 / 9 | |
| 5.0.4 | 12 / 6 | |
| 5.0.3 | 12 / 6 | |
| 5.0.2 | 12 / 6 | |
| 5.0.1 | 12 / 6 | |
| 5.0.0 | 12 / 6 | |
| 4.0.14 | 14 / 6 | |
| 4.0.13 | 14 / 6 | |
| 4.0.12 | 14 / 6 | |
| 4.0.11 | 14 / 4 | |
| 4.0.10 | 14 / 4 | |
| 4.0.9 | 14 / 4 | |
| 4.0.8 | 12 / 4 | |
| 4.0.7 | 12 / 4 | |
| 4.0.6 | 12 / 4 | |
| 4.0.5 | 12 / 4 | |
| 4.0.4 | 12 / 4 | |
| 4.0.3 | 12 / 4 | |
| 4.0.2 | 12 / 3 | |
| 4.0.1 | 12 / 3 | |
| 4.0.0 | 12 / 3 | |
| 3.0.3 | 11 / 3 | |
| 3.0.2 | 11 / 2 | |
| 3.0.1 | 11 / 7 | |
| 3.0.0 | 11 / 7 | |
| 2.0.1 | 11 / 7 | |
| 2.0.0 | 11 / 7 | |
| 1.2.0 | 11 / 7 | |
| 1.1.1 | 11 / 7 | |
| 1.1.0 | 11 / 7 | |
| 1.0.1 | 10 / 7 |
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (reggi) than the most recent previously approved version (owlstronaut) on 2026-07-08, but reggi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (owlstronaut) than the most recent previously approved version (gar) on 2026-03-18, but owlstronaut is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.