The package is clearly documented, licensed, and has a small dependency footprint. It is maintained by one individual, with no security policy or scanning and no recent repository activity, so future support is uncertain.
61%
Total Score
50
100
88
50
Only one registry maintainer account is listed. The linked repository is also user-owned rather than organization-owned, leaving limited visible redundancy if that maintainer becomes unavailable.
The package has 28 releases over more than 11 years, but none in the last 12 months; the latest release was about 1 year and 10 months ago. This long release gap weakens confidence in ongoing maintenance.
The repository had zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is a meaningful abandonment risk for a plugin that may need compatibility updates.
The repository uses Composer, showing a defined build tool, but it reports no security scanning tools. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy. This leaves vulnerability reporting and response expectations unclear, adding a maintenance and transparency concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version >=1.0.8 | — | — |
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.