The MIT license, README, and release notes provide useful baseline transparency. Maintenance has effectively stopped, and the repository has no security policy or scanning evidence, so pinning this old integration creates substantial support and compatibility risk.
34%
Total Score
0
75
50
The package has had no release in more than 10 years, with zero releases in the last 12 months. That is strong evidence of abandonment for a framework integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This substantially raises the risk that compatibility issues will remain unfixed.
Composer build tooling is present, but no security-scanning tools were detected. The lack of scanning weakens maintenance hygiene for a package handling application database configuration.
The repository has no security policy. This is a transparency gap, though it does not by itself show that the package is unsafe.
The assessed release is 1.1.0, while the registry reports 1.0.2 as the latest version, creating uncertainty about current version tracking. It is not marked prerelease, which provides only limited compensation.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version 5.2.* | — | — |
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.