Take care of your `spawn()`
61%
Total Score
50
100
88
75
50
No build attestation, trusted publisher, or staged publishing is reported. This limits release transparency, though it is a secondary concern for this small package.
Only one registry account has publish access. The linked repository is also owned by an individual, so there is no organizational backing shown to compensate for this thin maintainer base.
The package has only 3 releases across 3,165 days, with no releases in the last 12 months and a median interval of about 3.4 years. This indicates limited maintenance momentum, although the latest release is stable and the repository was updated with it.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Combined with the sparse release history, this is evidence of stalled maintenance rather than active development.
The repository reports no build tool and no security scanning tools. The simple source tree limits the impact of the missing build system, but the absent security scanning is still a hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cross-spawn Version ^7.0.5 | — | — |
signal-exit Version ^4.0.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.