cross-spawn

v7.0.3

Cross platform child_process#spawn and child_process#spawnSync For more information about how to use this package see README

Latest version published 4 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

70 / 100

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
7.0.3 | 05/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.5 | 03/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.1.0 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.2 | 09/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1 | 05/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (71,911,415)

Download trend
GitHub Stars
1.07K
Forks
71
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package cross-spawn receives a total of 71,911,415 downloads a week. As such, we scored cross-spawn popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package cross-spawn, we found that it has been starred 1,074 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the cross-spawn repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like cross-spawn is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 70/100 package health 70/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
16
Open PR
2
Last Release
4 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of cross-spawn based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for cross-spawn is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>= 8

Age
10 years
Dependencies
3 Direct
Versions
55
Install Size
21.2 kB
Dist-tags
1
# of Files
10
Maintainers
1
TS Typings
Yes

cross-spawn has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.