The project includes a clear README, tests, and an explicit MIT license. A solo maintainer and no repository security policy leave less support depth than a mature dependency.
58%
Total Score
50
86
83
One registry maintainer is a modest support and continuity risk for a user-owned project, although it does not by itself indicate abandonment.
Only two releases appeared over roughly 11 months, with both released within the first week; this is limited evidence of sustained maintenance for a young package.
The repository recorded zero commits and zero active maintainers in the last three months, while its last push was about 11 months ago; this materially lowers confidence in ongoing maintenance.
Composer build tooling is present, but no security-scanning tools were detected, leaving a repository hygiene gap without making the package unfit to use.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^12.0 | — | — |
illuminate/queue Version ^12.0 | — | — |
illuminate/support Version ^12.0 | — | — |
bensedev/type-guard Version ^1.0 | — | — |
illuminate/database 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.