Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Apr 27, 2024 via pnpm

npm-run-all 4.1.5

A CLI tool to run multiple npm-scripts in parallel or sequential.
Package summary
Share
3
issues
1
high severity
license
1
2
low severity
license
2
6
licenses
99
MIT
6
ISC
2
Apache-2.0
3
other licenses
BSD-2-Clause
1
CC-BY-3.0
1
CC0-1.0
1
Package created
24 Mar 2015
Version published
24 Nov 2018
Maintainers
1
Total deps
110
Direct deps
9
License
MIT

Issues

3

1 high severity issue

high
Recommendation: Read and validate the license terms
via: read-pkg@3.0.0
Collapse
Expand

2 low severity issues

low
Recommendation: Read and validate the license terms
via: read-pkg@3.0.0
Recommendation: Read and validate the license terms
via: read-pkg@3.0.0
Collapse
Expand

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
99 Packages, Including:
ansi-styles@3.2.1
array-buffer-byte-length@1.0.1
arraybuffer.prototype.slice@1.0.3
available-typed-arrays@1.0.7
balanced-match@1.0.2
brace-expansion@1.1.11
call-bind@1.0.7
chalk@2.4.2
color-convert@1.9.3
color-name@1.1.3
concat-map@0.0.1
cross-spawn@6.0.5
data-view-buffer@1.0.1
data-view-byte-length@1.0.1
data-view-byte-offset@1.0.0
define-data-property@1.1.4
define-properties@1.2.1
error-ex@1.3.2
es-abstract@1.23.3
es-define-property@1.0.0
es-errors@1.3.0
es-object-atoms@1.0.0
es-set-tostringtag@2.0.3
es-to-primitive@1.2.1
escape-string-regexp@1.0.5
for-each@0.3.3
function-bind@1.1.2
function.prototype.name@1.1.6
functions-have-names@1.2.3
get-intrinsic@1.2.4
get-symbol-description@1.0.2
globalthis@1.0.3
gopd@1.0.1
has-bigints@1.0.2
has-flag@3.0.0
has-property-descriptors@1.0.2
has-proto@1.0.3
has-symbols@1.0.3
has-tostringtag@1.0.2
hasown@2.0.2
internal-slot@1.0.7
is-array-buffer@3.0.4
is-arrayish@0.2.1
is-bigint@1.0.4
is-boolean-object@1.1.2
is-callable@1.2.7
is-core-module@2.13.1
is-data-view@1.0.1
is-date-object@1.0.5
is-negative-zero@2.0.3

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
6 Packages, Including:
graceful-fs@4.2.11
hosted-git-info@2.8.9
isexe@2.0.0
minimatch@3.1.2
semver@5.7.2
which@1.3.1

Apache License 2.0

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
use-patent-claims
place-warranty
Cannot
hold-liable
use-trademark
Must
include-copyright
include-license
state-changes
include-notice
2 Packages, Including:
spdx-correct@3.2.0
validate-npm-package-license@3.0.4

BSD 2-Clause "Simplified" License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
place-warranty
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
normalize-package-data@2.5.0

Creative Commons Attribution 3.0 Unported

Uncategorized
Not OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
Cannot
Must
1 Packages, Including:
spdx-exceptions@2.5.0

Creative Commons Zero v1.0 Universal

Public Domain
Not OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
Cannot
Must
1 Packages, Including:
spdx-license-ids@3.0.17
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

9
All Dependencies CSV
β“˜ This is a list of npm-run-all 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
ansi-styles3.2.13.72 kBMIT
prod
chalk2.4.29.63 kBMIT
prod
cross-spawn6.0.57.32 kBMIT
prod
memorystream0.3.15.39 kBMIT
prod
minimatch3.1.211.66 kBISC
prod
pidtree0.3.16.52 kBMIT
prod
read-pkg3.0.01.99 kBMIT
prod
1
2
shell-quote1.8.115.23 kBMIT
prod
string.prototype.padend3.1.61 BMIT
prod

Visualizations

Frequently Asked Questions

What does npm-run-all do?

The npm-run-all is a powerful Command Line Interface (CLI) tool that allows running of multiple npm scripts either sequentially or in parallel. This tool does not only simplify the process of running multiple scripts by utilizing the glob-like patterns, but it also enhances cross-platform usability by providing compatibility with both Unix/Linux and Windows operating systems.

How do you use npm-run-all?

To use npm-run-all, it has to be first installed in your project with the command npm install npm-run-all --save-dev, or if you're using Yarn as package manager, use yarn add npm-run-all --dev. This command will install npm-run-all as dev-dependency in your project.

Now, you can add the scripts to be run either in parallel or sequentially in your npm scripts section in package.json file. If you want to run the scripts sequentially use -s and for parallel execution use -p.

Use it as follows in your package.json:

"scripts": {
  "clean": "action for clean",
  "build:css": "action for build:css",
  "build:js": "action for build:js",
  "build:html": "action for build:html",
  "build": "npm-run-all -s clean build:*"
}

Now, if you run npm run build in the terminal, it'll execute the clean script and then all build scripts sequentially.

For parallel execution change -s to -p in the build command:

"scripts": {
  "script1": "action for script1",
  "script2": "action for script2",
  "script3": "action for script3",
  "start": "npm-run-all -p script*"
}

In this case, executing npm run start will initiate script1, script2, and script3 in parallel.

Where are the npm-run-all docs?

The npm-run-all documentation is located within the project's Github repository. The detailed guides for using npm-run-all and its sub-commands (run-s and run-p) are provided in separate markdown files. These guides can be accessed via the following links: