kill trees of processes
57%
Total Score
25
100
90
75
50
There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this is the strongest abandonment concern in the collected evidence.
No build attestation or trusted-publisher provenance is present. This is a transparency gap, but for this small, directly structured package it is not severe enough to determine the health band alone.
The package has 13 releases since April 2013, but its latest release was in December 2019 and there were no releases in the last 12 months. This is a meaningful maintenance concern for a dependency.
The repository has 20 open issues and 4 open pull requests, while none were closed or merged in the last month. This suggests limited responsiveness alongside the broader maintenance slowdown.
The repository uses no build tooling and has no security scanning tools. The simple package structure makes the lack of a build system less concerning, but the absent security scanning reduces maintenance transparency.
| Title | Versions | Severity |
|---|---|---|
CVE-2019-15598 tree-kill is vulnerable to Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in versions 0.0.0 - 1.2.2. | 0.0.0 - 1.2.2 | Critical |
CVE-2019-15599 tree-kill is vulnerable to Improper Control of Generation of Code ('Code Injection') in versions 0.0.0 - 1.2.2. | 0.0.0 - 1.2.2 | Critical |
No direct dependencies.
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.