The stable release, matching source repository, MIT license, and release notes improve transparency. Its small dependency set and lack of install scripts reduce adoption risk, but there is no security policy or scanning evidence.
34%
Total Score
25
100
79
75
The latest release was published in October 2016, with no releases in the last 12 months across roughly ten years of package age. This is strong evidence of abandonment for a framework integration package.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving current maintenance capacity un demonstrated.
The repository is owned by the same individual account as the registry namespace. That provides consistent ownership, but no organization backing or broader maintenance capacity is shown.
Composer is used for the build, but the repository reports no security scanning tools. That is a modest transparency gap, especially for an old package, though it is not evidence of a defect by itself.
No security policy is present in the repository, leaving no documented process for reporting or handling vulnerabilities. The package's age and inactivity make this gap more consequential.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^5.2 | — | — |
illuminate/database 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.