The package has a clear README, a compact dependency set, and no install-time scripts. The linked source is intact and identifies the package, but its small project footprint offers little evidence of future support.
38%
Total Score
0
100
64
83
No license is declared, detected, or included in the package, and the linked repository also has no license file. This creates a real legal and transparency risk for adoption.
The latest release was published about eight years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package developers would depend on.
The repository had no commits and no active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
The repository uses Make and Composer, showing basic build tooling, but it has no security-scanning tools. This is a modest hygiene gap rather than a standalone adoption blocker.
The repository has no security policy. For a small command-line package this is a transparency gap, though it is less significant than the lack of maintenance and licensing.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wp-cli/php-cli-tools Version * | — | — |
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.