Gathering detailed insights and metrics for yarn-run-all
Gathering detailed insights and metrics for yarn-run-all
Installations
npm install yarn-run-allDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>= 0.10
Node Version
6.9.1
NPM Version
3.10.8
Score
57.1
Supply Chain
94.7
Quality
73.2
Maintenance
50
Vulnerability
99.6
License
Releases
51
Contributors
22
Languages
1
JavaScript
JavaScript (100%)
Developer
mysticatea
Download Statistics
Total Downloads
5,244,021
Last Day
1,043
Last Week
12,925
Last Month
80,077
Last Year
1,504,429
GitHub Statistics
5,761 Stars
267 Commits
242 Forks
35 Watching
4 Branches
22 Contributors
Maintainers
1
Package Meta Information
Latest Version
3.1.1
Package Id
yarn-run-all@3.1.1
Size
15.56 kB
NPM Version
3.10.8
Node Version
6.9.1
Publised On
26 Oct 2016
Total Downloads
Cumulative downloads
Total Downloads
5,244,021
Last day
-68.4%
1,043
Compared to previous day
Last week
-31.7%
12,925
Compared to previous week
Last month
-19.3%
80,077
Compared to previous month
Last year
26.7%
1,504,429
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
| index | npm-run-all | run-s | run-p | Node API |
|---|
npm-run-all
A CLI tool to run multiple npm-scripts in parallel or sequential.
$ npm-run-all clean lint build:*
$ npm-run-all --parallel watch:*
Installation
$ npm install npm-run-all
- Requires
Node@>=0.10andnpm@>=2 - The
npm-run-allpackage introduces 3 CLI commands:npm-run-all,run-s, andrun-p.
CLI Commands
This npm-run-all package provides 3 CLI commands.
The main command is npm-run-all. We can make complex plans with npm-run-all command.
Both run-s and run-p are shorthand commands. run-s is for sequential, run-p is for parallel. We can make simple plans with those commands.
Node API
This npm-run-all package provides Node API.
Changelog
Contributing
Thank you for contributing!
Bug Reports or Feature Requests
Please use GitHub Issues.
Correct Documents
Please use GitHub Pull Requests.
I'm not familiar with English, so I especially thank you for documents' corrections.
Feature Implementing
Please use GitHub Pull Requests.
There are some npm-scripts to help developments.
Those work on Windows, Mac, or Linux (by the way, I'm developping npm-run-all on Windows).
- npm test - Run tests and collect coverage.
- npm run build - Make
libdirectory fromsrcdirectory. - npm run clean - Delete directories (folders) which are created by other commands.
- npm run lint - Run ESLint.
- npm run watch - Run tests (not collect coverage) when each file was modified.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 existing vulnerabilities detected
Reason
Found 6/30 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 6 are checked with a SAST tool
Score
3.3
/10
Last Scanned on 2024-12-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More