The small command-line package is clearly documented and has a straightforward dependency set. Its last release and repository activity were about eight years ago, with one maintainer and no security tooling, making abandonment the main concern.
42%
Total Score
25
100
72
75
The package has had no release in about eight years and none in the last 12 months, despite 22 releases overall. This is strong evidence of abandonment risk for a dependency, although the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided signal shows current maintenance capacity.
Only one registry publishing account is listed. That is a thin maintainer base and increases continuity risk, though it does not by itself indicate the package is unsafe.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no additional community or continuity signal to offset the inactive maintenance record.
The project uses Composer and Make, which supports reproducible project tasks, but it has no security scanning tools. This is a modest transparency and maintenance gap rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wp-cli/php-cli-tools Version ^0.11.9 | — | — |
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.