A clear README, tests, MIT licensing, and an organization-backed repository make adoption easier. The absence of a security policy and scanning leaves maintenance assurance limited.
62%
Total Score
75
100
83
75
The package has 11 releases over about seven years, but none in the last two years and three months. That indicates a mature but currently inactive release cadence.
There were no commits and no active maintainers in the last three months, consistent with the last push being about two years and three months ago. This is the clearest abandonment concern.
The repository has one star and two forks, showing limited external adoption. Popularity is supporting evidence rather than a decisive health measure, but it provides little independent validation.
Composer build tooling is present, but no security scanning tools are configured. The build setup is appropriate, while the missing scanning reduces transparency around ongoing maintenance.
The repository has no security policy. This does not make the package unsafe by itself, but it leaves vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/events Version ~5.8.0|6.*|7.*|8.*|9.*|10.*|11.* | — | — |
illuminate/support Version ~5.8.0|6.*|7.*|8.*|9.*|10.*|11.* | — | — |
illuminate/database Version ~5.8.0|6.*|7.*|8.*|9.*|10.*|11.* | — | — |
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.