MIT licensing, included tests, and a repository that matches the package make the code easier to inspect. Its small dependency set and lack of install-time scripts reduce integration friction, but they do not offset the maintenance concern.
34%
Total Score
0
75
50
The package has only one release, published about 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a framework integration package.
There were no commits or active maintainers in the last 3 months, consistent with the repository's last push being about 10 years ago. This materially increases abandonment risk.
The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these counters provide no meaningful community-maintenance buffer.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. That is a modest hygiene gap rather than evidence the package is unsafe.
The repository has no security policy. For a package with no recent maintenance, this further weakens transparency and vulnerability-reporting expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/events Version 5.1.*|5.2.* | — | — |
illuminate/session Version 5.1.*|5.2.* | — | — |
illuminate/support Version 5.1.*|5.2.* | — | — |
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.