Laravel Module management
70%
Total Score
50
100
89
67
The registry namespace and repository are owned by the same individual account, providing a clear project owner. A single individual owner offers less organizational continuity than established team backing.
The package has existed for over 10 years with 115 releases, but only 2 releases occurred in the last 12 months. The long history compensates for the slower recent cadence, though it warrants monitoring.
The repository recorded zero commits and zero active maintainers over the last 3 months. The recent release and push provide some compensating evidence, but the current maintenance pause is a meaningful abandonment risk.
The repository has 14 open issues and 10 open pull requests, but no issues were closed in the last month and no pull requests were merged. This indicates some short-term maintenance backlog.
Composer build tooling is present, but no security-scanning tools were detected. This is a transparency and process gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wikimedia/composer-merge-plugin Version ^2.1 | — | — |
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.