A CLI tool to run multiple npm-scripts in parallel or sequential.
62%
Total Score
50
100
89
83
The repository is owned by an individual account rather than an organization. This does not establish poor health, but it means there is no provided evidence of organizational backing to offset the thin maintenance picture.
The latest registry release was published nearly eight years ago, with no releases in the last 12 months. Its 58-release history shows earlier development, but the long gap lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. This strongly supports the conclusion that active maintenance has slowed or stopped.
There were no new or closed issues or pull requests in the last month, with 102 open issues and 12 open pull requests. This indicates limited current project activity.
The repository uses Babel and npm scripts for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^2.4.1 | — | — |
pidtree Version ^0.3.0 | — | — |
read-pkg Version ^3.0.0 | — | — |
minimatch Version ^3.0.4 | — | — |
ansi-styles Version ^3.2.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.