The source repository has seen no commits or releases for about 11 years, with no recent maintainer activity. A README and MIT license help, but absent security tooling and policy leave this old dependency with substantial maintenance risk.
39%
Total Score
0
71
75
The last release was published about 11 years ago, and there were no releases in the last 12 months. Although the package had five releases early in its life, the long release gap materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for about 11 years.
Composer is used for builds, but no security scanning tools are configured. For an old package with no recent maintenance, this leaves dependency and build risks less actively monitored.
The linked repository is not marked archived, but its last push was about 11 years ago. The active archive status does not compensate for the prolonged lack of activity.
The repository has no security policy. This is a transparency gap, especially for a package whose maintenance activity has already stopped.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
kilahm/hack-clio Version ~1.1.0 | — | — |
hackpack/hack-class-scanner Version 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.