MIT licensing, a matching repository, tests, and a usable README improve transparency. The single maintainer and absent security scanning leave little operational reassurance.
38%
Total Score
33
71
50
The package has only one release, published over 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a framework-based dependency.
There were no commits and no active maintainers in the last 3 months, reinforcing the release history's evidence that development has stopped.
Only one registry maintainer is listed, and the project is user-owned rather than organization-backed. This creates a thin publishing and continuity base.
There were no new or closed issues or pull requests in the last month. Combined with the lack of commits, this suggests an inactive project rather than a healthy quiet period.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence of maliciousness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
artesaos/defender Version ^0.4.6 | — | — |
laravel/framework Version 5.1.* | — | — |
prettus/l5-repository Version ^2.1 | — | — |
acacha/admin-lte-template-laravel Version 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.