The documentation is substantial, the dependency surface is small, and the release includes tests and notes. A single active maintainer and an unpinned workflow reduce resilience, while the missing security policy leaves less transparency for incident handling.
65%
Total Score
50
100
94
75
One registry maintainer is consistent with the individually owned repository, but it also indicates limited publishing redundancy.
The repository is owned by an individual rather than an organization, so the concentrated maintainer and contributor activity has no organizational backing to compensate for it.
One contributor made 100% of the commits in the last three months, leaving little demonstrated handoff capacity for a user-owned project.
Only one commit was recorded in the last three months, so recent direct maintenance activity is limited despite recent release and pull-request activity elsewhere.
Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0|^13.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.