Clear licensing, a substantial README, and no install-time scripts reduce adoption and supply-chain friction. Recent work is visible, but maintenance depends entirely on one contributor and the repository has no security policy or scanning.
70%
Total Score
63
94
75
One registry maintainer is consistent with a user-owned project, but it reinforces the single-person maintenance concentration shown by recent repository activity.
The repository is owned by an individual rather than an organization, so there is no shown organizational backing to offset the concentrated contributor base.
All 11 recent commits came from one contributor, so maintenance continuity depends on a single person despite the current activity.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
The repository has no documented security policy, reducing transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^v11|^v12|^v13 | — | — |
illuminate/config Version ^v11|^v12|^v13 | — | — |
illuminate/console Version ^v11|^v12|^v13 | — | — |
illuminate/support Version ^v11|^v12|^v13 | — | — |
illuminate/collections Version ^v11|^v12|^v13 | — | — |
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.