The package has had no release for about five years and no recent repository commits, which raises maintenance risk. Clear licensing, tests, documentation, and a non-archived repository provide useful support, but there is no security policy.
58%
Total Score
75
81
50
The latest release was about five years ago, with no releases in the last 12 months. The five releases arrived at roughly weekly intervals initially, but the prolonged gap now raises abandonment risk.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates that fixes and compatibility updates may not be forthcoming.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk.
The linked repository is not archived, but it was last pushed about four years ago. That preserves access to the source while reinforcing the maintenance concern shown by the release history.
The repository has no security policy. For a small plugin this is a limited transparency gap, but it leaves vulnerability-reporting expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0 | — | — |
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.