The project has a clear license, tests and changelog in its repository, and a recent stable release. Its small single-person maintainer base, sparse release cadence, and lack of a security policy leave limited operational depth.
72%
Total Score
50
100
88
83
The package and repository are both owned by the same individual account. That is coherent ownership, but it provides less organizational continuity than a backed project.
The package is about 10 years old but has only 7 releases, with a median interval of about 20 months and 1 release in the last year. The recent release shows continued maintenance, though the cadence is sparse.
No commits or active maintainers were recorded in the preceding 3 months. The April 2026 release and repository push show recent activity, but the short-term contributor activity remains limited.
The repository uses Composer for builds, but no security scanning tools were detected. For a small library this is a modest transparency gap, not evidence of an unsafe release.
No repository security policy was found, leaving no documented channel or process for reporting vulnerabilities.
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.