The project has had no commits or releases for about 16 months, and one person maintains a tiny repository without security scanning or a security policy. It remains clearly packaged, licensed, documented, and non-deprecated.
58%
Total Score
25
100
78
88
There were zero commits and zero active maintainers during the last three months, consistent with the long gap since the initial release burst and increasing abandonment risk.
One registry maintainer is consistent with a small user-owned project, but it also indicates limited publishing capacity if the sole maintainer becomes unavailable.
All four releases arrived within about five hours on May 28, 2025, followed by no releases for about 16 months. This suggests an immature or inactive release history.
The repository has zero stars and one fork. Popularity is only supporting evidence, but these counters provide little external evidence of maturity.
Composer build tooling is present, but no security scanning tools were detected. For a small PHP library this is a meaningful maintenance and transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bcosca/fatfree Version * | — | — |
poliander/cron Version ^3.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.