Process execution for humans
88%
Total Score
healthy
A mature, actively maintained package is held back by concentrated recent development and unpinned workflow actions.
The repository is owned by a user account rather than an organization, so the concentrated recent contributor activity is not offset by explicit organization backing. The active project history still provides meaningful support.
One contributor made all 35 commits in the last three months, giving the project a concentrated recent maintenance base. The long project history and active repository reduce but do not remove this continuity risk.
The repository uses TypeScript, Gulp, and npm scripts, demonstrating a real build process. No security-scanning tools were detected, which is a modest transparency gap but not decisive given the other evidence.
The single workflow was fully analyzed with no untrusted checkouts, injection findings, or audit findings, and it has no broad top-level write permission. All five action references are unpinned, however, leaving build inputs less reproducible.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
figures Version ^6.1.0 | — | — |
is-stream Version ^4.0.1 | — | — |
pretty-ms Version ^9.3.1 | — | — |
get-stream Version ^9.0.1 | — | — |
signal-exit Version ^4.1.0 | — | — |
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.