</>PackageGraphPackageGraph

cross-spawn

npmv7.0.6

Cross platform child_process#spawn and child_process#spawnSync

Adopt with care

cross-spawn is usable, with caveats. Last published 660 days ago. 4 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • CMaintenance: grade C, Fair — worth a look.

    Last published 660 days ago. 4 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 5 transitive packages, about 95 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding cross-spawn to a project.

3
Direct dependencies

Runtime packages this one declares itself.

5
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

95 KB
Install size

Unpacked size of this package plus its entire runtime tree.

2
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

BlueOak-1.0.0ISCMIT

Every license you inherit by installing cross-spawn, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 8
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the cross-spawn README.

const spawn = require('cross-spawn');

// Spawn NPM asynchronously
const child = spawn('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });

// Spawn NPM synchronously
const result = spawn.sync('npm', ['list', '-g', '-depth', '0'], { stdio: 'inherit' });

cross-spawn vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
cross-spawnthis page09MIT1 year ago
path-key244.9M1MIT17 hours ago
open130.4M4MIT14 hours ago
log-symbols01MIT14 hours ago
shebang-command01MIT18 hours ago
is-wsl117.6M4MIT19 hours ago

Dependencies

Declared by cross-spawn v7.0.6. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (13)

@commitlint/cli ^8.1.0@commitlint/config-conventional ^8.1.0babel-core ^6.26.3babel-jest ^24.9.0babel-preset-moxy ^3.1.0eslint ^5.16.0eslint-config-moxy ^7.1.0husky ^3.0.5jest ^24.9.0lint-staged ^9.2.5mkdirp ^0.5.1rimraf ^3.0.0standard-version ^9.5.0

Used by

Popular packages that depend on cross-spawn.

Relationship graph

Dependencies (left) and dependents (right) of cross-spawn.

Frequently installed together

Release history

No releases in the last two years, typically about 31 days apart.

Recent versions of cross-spawn
VersionPublishedSizeLicense
6.0.61 year ago18 KBMIT
7.0.6latest1 year ago16 KBMIT
7.0.51 year ago16 KBMIT
7.0.41 year ago16 KBMIT
7.0.36 years ago21 KBMIT
7.0.26 years ago20 KBMIT
7.0.17 years ago20 KBMIT
7.0.07 years ago20 KBMIT
6.0.58 years ago21 KBMIT
6.0.48 years agoMIT
6.0.38 years agoMIT
6.0.28 years agoMIT
6.0.18 years agoMIT
6.0.08 years agoMIT
5.1.09 years agoMIT

Overview

cross-spawn is an npm package that cross platform child_process#spawn and child_process#spawnSync. It has 9 known dependents in the graph. The latest version is 7.0.6, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need cross platform child_process#spawn and child_process#spawnSync and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • Large dependency tree (16 direct dependencies) increases install size and audit surface.
  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use cross-spawn?

cross-spawn is usable, with caveats. Last published 660 days ago. 4 releases in the last 2 years.

How do I install cross-spawn?

Run `npm install cross-spawn` to add cross-spawn to your npm project.

How many dependencies does cross-spawn have?

cross-spawn declares 16 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 95 KB on disk.

What license is cross-spawn released under?

cross-spawn is distributed under the MIT license. Its dependency tree also includes: BlueOak-1.0.0, ISC, MIT.

How popular is cross-spawn?

npm does not publish download counts. Within PackageGraph's crawl, 9 known packages depend on cross-spawn.

Is cross-spawn still maintained?

The most recent release of cross-spawn (v7.0.6) was published 1 year ago.

Does cross-spawn run install scripts?

No. cross-spawn does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.