npm-run
Run executables for locally-installed packages without using ./node_modules/.bin
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:serializerr | AI (phantom-deps): serializerr is a declared dependency legitimately used for error serialization; phantom-dep finding is a false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): cross-spawn is a well-known, widely-trusted cross-platform spawn utility; its addition is a legitimate improvement for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): npm-run's core purpose is executing local package binaries; child_process usage is fundamental and expected for this package. | ai | |
| dependencies | unvetted-dep:sync-exec | AI (dependencies): sync-exec is a pre-existing dependency consistent with npm-run's purpose of synchronously resolving and running executables. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 4 / 3 | |
| 5.0.0 | 4 / 3 | |
| 4.1.2 | 6 / 3 | |
| 4.1.1 | 6 / 3 | |
| 4.1.0 | 6 / 2 | |
| 4.0.1 | 5 / 2 | |
| 4.0.0 | 5 / 2 | |
| 3.0.0 | 5 / 2 | |
| 2.0.0 | 6 / 2 | |
| 1.1.1 | 4 / 3 | |
| 1.1.0 | 4 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.