Clear licensing, tests, and a complete README support straightforward integration. The long release gap and currently quiet commit history leave maintenance uncertain, despite a repository push in February 2025.
65%
Total Score
50
100
88
88
One registry maintainer account indicates a thin publishing base. Because the repository is user-owned rather than organization-backed, there is no provided organizational backing to offset that concern.
The repository is owned by the same individual namespace as the package and is user-backed rather than organization-backed. This is consistent ownership, but it offers limited redundancy if the maintainer becomes unavailable.
The package has 20 releases over more than 12 years, but none in the last 12 months and its latest registry release was in August 2022. This is a meaningful maintenance concern.
There were zero commits and zero active maintainers in the last three months. Although the repository was pushed in February 2025, the measured recent activity remains quiet and adds abandonment uncertainty.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
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.