The package has tests, a changelog, a matching repository, and a clear MIT license. Maintenance has gone quiet since November 2025, while the sole registry maintainer and unpinned workflow actions add ongoing upkeep risk.
58%
Total Score
33
88
83
There were no commits and no active maintainers in the three months before collection, a concrete sign that maintenance has stalled after the latest release.
One registry account publishes the package, which creates a narrow publishing base; the matching personal repository provides some continuity but does not remove the single-maintainer risk.
The registry namespace and repository owner match, but the backing is a personal account rather than an organization, so institutional continuity is limited.
The package has 8 releases, all within the last 12 months, but the latest release was about 10 months before collection, leaving a meaningful recent-maintenance gap.
The project uses Composer build tooling, but no security scanning tools were detected, leaving a modest repository-hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/bus Version ^12.0 | — | — |
illuminate/cache Version ^12.0 | — | — |
guzzlehttp/guzzle Version ^7.10 | — | — |
illuminate/config Version ^12.0 | — | — |
illuminate/events Version ^12.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.