run-p

v0.0.0

A shorthand of npm-run-all

MIT
Latest version published 6 years ago
    npm install run-p
  

Package Health Score

56 / 100

Security

No known security issues
Powered by Snyk
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
0.0.0 | 04/2016
Popular
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test run-p
Get started free

Popularity

Recognized

Weekly Downloads (3,811)

Download trend
Dependents
30.82K
GitHub Stars
4.77K
Forks
253
Contributors
30

Direct Usage Popularity

Uncommon

The npm package run-p receives a total of 3,811 downloads a week. As such, we scored run-p popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package run-p, we found that it has been starred 4,773 times, and that 30,824 other projects in the ecosystem are dependent on it.

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
30
Funding
Yes

With more than 10 contributors for the run-p 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 run-p is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
77
Open PR
11
Last Release
6 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of run-p 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 run-p 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
0 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

run-p 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.