npm-run-all MIT 51 versions

npm-run-all

npm Repository Homepage

A CLI tool to run multiple npm-scripts in parallel or sequential.

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

mysticatea

Keywords

clicommandcommandlinetoolnpmnpm-scriptsrunsequentialserialparalleltask

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): npm-run-all's core function is spawning npm script processes; child_process.spawn usage is inherent and expected for this package across all versions.	ai	2026/04/22
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads help modules by CLI subcommand name — a standard, safe pattern for this CLI tool's architecture.	ai	2026/04/22
semgrep	semgrep:env-bulk-read	AI (semgrep): Reading process.env keys is core functionality: npm-run-all passes npm_package_config_* variables to scripts by design.	ai	2026/04/22

Versions (showing 51 of 56)

View all versions

Version	Deps	Published
4.1.5	9 / 14	2018-11-24
4.1.4	8 / 15	2018-11-24
4.1.3	9 / 15	2018-05-06
4.1.2	9 / 15	2017-11-07
4.1.1	9 / 12	2017-08-28
4.1.0	8 / 12	2017-08-26
4.0.2	7 / 11	2017-02-22
4.0.1	7 / 11	2017-01-17
4.0.0	7 / 11	2016-12-31
3.1.2	10 / 14	2016-12-01
3.1.1	10 / 13	2016-10-15
3.1.0	10 / 13	2016-09-01
3.0.0	10 / 13	2016-08-17
2.3.0	10 / 13	2016-06-28
2.2.2	10 / 13	2016-06-23
2.2.1	10 / 13	2016-06-23
2.2.0	10 / 13	2016-06-18
2.1.2	10 / 13	2016-06-12
2.1.1	10 / 13	2016-05-19
2.1.0	10 / 13	2016-05-13
2.0.0	10 / 13	2016-05-11
1.8.0	8 / 17	2016-04-24
1.7.0	5 / 17	2016-03-29
1.6.0	5 / 17	2016-03-19
1.5.3	5 / 17	2016-03-12
1.5.2	5 / 17	2016-03-08
1.5.1	5 / 17	2016-01-28
1.5.0	5 / 17	2016-01-16
1.4.0	5 / 15	2015-12-08
1.3.4	5 / 15	2015-12-06
1.3.3	5 / 15	2015-12-02
1.3.2	5 / 12	2015-11-23
1.3.1	3 / 13	2015-11-18
1.3.0	4 / 11	2015-11-18
1.2.13	3 / 13	2015-11-05
1.2.12	3 / 13	2015-10-17
1.2.11	3 / 12	2015-09-07
1.2.10	3 / 12	2015-09-07
1.2.9	3 / 12	2015-09-07
1.2.8	3 / 12	2015-08-26
1.2.7	3 / 12	2015-08-26
1.2.6	3 / 11	2015-06-19
1.2.5	2 / 10	2015-05-15
1.2.4	2 / 10	2015-04-26
1.2.3	2 / 11	2015-04-18
1.2.2	2 / 8	2015-04-15
1.2.1	2 / 7	2015-04-15
1.2.0	2 / 7	2015-04-15
1.1.3	0 / 7	2015-04-11
1.1.2	0 / 7	2015-04-04
1.1.1	0 / 7	2015-03-30

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.