The MIT license, release notes, matching repository, and lack of install scripts improve transparency and adoption safety. A single maintainer, no security policy, and no automated security scanning limit confidence in long-term support.
57%
Total Score
50
88
75
Only one account has package publish access. Because the project is backed by an individual repository owner, this indicates a thin maintainer base and limited continuity if that person stops maintaining it.
The package has had only one release, with no registry release for about 2 years 7 months. That is a meaningful maintenance concern despite the repository being updated more recently.
There were zero commits and zero active maintainers in the last 3 months. Combined with the single-release history, this weakens evidence of active ongoing development.
Composer build tooling is present, but no security scanning tools were detected. The missing security automation is a modest transparency and maintenance gap.
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/support Version ^5.5|^6.0|^7.0|^8.0 | — | — |
illuminate/database Version ^5.5|^6.0|^7.0|^8.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.