59%
Total Score
caution
Usable with caveats: the sole release is over four years old despite a repository push in 2025.
Only one registry account has publish access. Because the project is backed by an individual repository owner, this is not automatically a problem, but it leaves limited observable publishing redundancy.
This package has only one release, published over four years ago, with no releases in the last 12 months. That is a meaningful sign of limited release maintenance, although the repository was pushed more recently.
The repository recorded no commits and no active maintainers in the last three months. The June 2025 push is a compensating sign, but current activity remains too limited to establish active maintenance.
The repository uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. That limits the documented process for reporting and handling vulnerabilities, though it does not by itself show a vulnerability.
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.