Risky to adopt for a new project: the package has had no release since June 2017 and no recent repository activity. It remains licensed, documented, tested, and not deprecated or archived, but its long abandonment period makes ongoing compatibility and maintenance a serious concern.
42%
Total Score
0
70
75
The latest release was in June 2017, with no releases in the last 12 months despite an established package history. Nearly nine years without a release is strong evidence of abandonment risk, even though the earlier release cadence was reasonably regular.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. This materially lowers confidence that compatibility or defects will be addressed.
The linked repository is not archived, which is a positive counter-signal, but it was last pushed in September 2017 and therefore does not offset the prolonged inactivity.
The repository has no security policy. This is a transparency gap, although the absence of workflows and the package's long inactivity limit the practical significance of this signal compared with the maintenance risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ~5.1 | — | — |
illuminate/support Version ~5.1 | — | — |
illuminate/database Version ~5.1 | — | — |
illuminate/validation Version ~5.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.