The README, tests, changelog, and MIT licensing provide a usable foundation. Its narrow dependency set and clean repository linkage help, but this should be replaced where possible rather than adopted for new production work.
42%
Total Score
25
100
75
75
The package has had only two releases, both in March 2017, with no releases in the last 12 months despite being about 9 years old. This is strong evidence of abandonment risk.
The repository has had no commits and no active maintainers in the last 3 months; its last push was in March 2019. The long inactivity materially lowers confidence in ongoing maintenance.
There have been no new or closed issues or pull requests in the last month, with two issues still open. This supports the broader picture of an inactive project.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap that adds modest maintenance risk.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency and maintenance gap, though not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.1 | — | — |
illuminate/database 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.