38%
Total Score
unhealthy
Risky: no releases or commits since May 2020, with minimal repository adoption.
The package has had no release in about six years: its latest release was published in May 2020, and it had zero releases in the last 12 months. This is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this materially raises abandonment risk.
Only one registry account has publish access. That is a narrow publishing base for an independently owned project and increases continuity risk if the maintainer stops responding.
The registry namespace and repository are owned by the same individual account, so the source appears correctly linked. The individual ownership offers less institutional backing than an organization-owned project.
There are no open issues or pull requests, and no recent issue or pull-request activity. This is consistent with a quiet project but does not show active maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/config Version ^5.5|^6.0|^7.0 | — | — |
illuminate/support Version ^5.5|^6.0|^7.0 | — | — |
illuminate/database Version ^5.5|^6.0|^7.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.