Usable with caveats: the package is small, licensed, tested, and clearly backed by its matching repository, but maintenance appears to have stopped after June 2025. The lack of recent commits and security safeguards makes it a less dependable choice for a long-lived dependency.
62%
Total Score
50
100
81
80
The registry namespace and repository owner match, and the project is owned by an individual rather than an organization. The single maintainer is therefore a real capacity concern, though the matching repository provides direct ownership transparency.
The package has five releases, but none were published in the last 12 months and the latest release was about 15 months before collection. That creates a meaningful maintenance concern despite the relatively short release intervals early in its history.
There were no commits and no active maintainers in the three months before collection, indicating that development activity has currently stopped.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and assurance gap, though it is not by itself evidence that the package is unsafe.
The linked repository is not archived, although its last push was about 15 months before collection, consistent with the maintenance concerns shown by release history.
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.