The package has a clear MIT license, matching source repository, and a usable README with few runtime dependencies. Its lack of recent releases or commits, plus no security policy or scanning, makes long-term maintenance uncertain.
58%
Total Score
50
100
86
75
The registry namespace and repository owner match a single individual account. This is consistent ownership, though it provides less continuity than organization backing.
The latest release was published about five years ago, with no releases in the last 12 months. This is a substantial maintenance concern for a framework plugin, despite the package having five releases overall.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates inactive maintenance and raises abandonment risk.
There were no new or closed issues or pull requests in the last month, while two issues and one pull request remain open. This supports the conclusion that current project activity is limited.
Composer is used for the build, but the repository has no security scanning tools. That is a modest transparency and maintenance gap, not a severe risk by itself.
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.