The clear README, MIT license, and small dependency surface help adoption. Its long release gap and inactive repository make compatibility and maintenance liability likely; pinning requires accepting an old Laravel 5 integration.
42%
Total Score
67
100
69
50
The package has had no release in more than 11 years, with only four releases and none in the last 12 months. This is strong evidence of abandonment risk for a framework integration.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being in 2017. This materially increases abandonment and unpatched-compatibility risk.
Composer build tooling is present, but no security-scanning tooling was detected. That is a modest transparency and maintenance gap, while the absence does not by itself indicate unsafe code.
The repository is not archived, which preserves a path for maintenance, but its last push was in January 2017 and does not compensate for the broader inactivity.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This adds a transparency gap to an already inactive project.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.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.