Run a lifecycle script for a package (descendant of npm-lifecycle)
84%
Total Score
67
100
94
100
100
All recent commits came from one contributor, creating a concentrated short-term bus factor. The risk is partly offset by the repository being owned by an organization with ongoing release infrastructure.
Only one commit was recorded in the last three months, so recent code activity is limited. However, the package released five times in the last year and has current release notes, making this a mild maintenance concern rather than abandonment evidence.
No type declarations are included. This is a modest integration gap for a JavaScript library consumed through an API, though it does not indicate abandonment or supply-chain weakness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
node-gyp Version ^13.0.0 | — | — |
proc-log Version ^7.0.0 | — | — |
@npmcli/node-gyp Version ^6.0.0 | — | — |
@npmcli/package-json Version ^8.0.0 | — | — |
@npmcli/promise-spawn Version ^10.0.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.