It has a clear README, changelog, repository tests, and a matching source repository. A single maintainer and no security policy add modest long-term maintenance risk.
62%
Total Score
50
100
88
75
Only one registry maintainer is listed, so publishing continuity depends heavily on a single person. The matching user-owned repository provides ownership context but does not offset the limited maintainer base.
The package has six releases over roughly 11 years, with no release in nearly four years and a median interval of about 14 months. This indicates substantially slowed maintenance for a dependency.
There were zero commits and zero active maintainers in the last three months. Although the repository is not archived, the lack of observed development activity raises abandonment risk.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and hygiene gap rather than a severe dependency risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The README's contact guidance provides some compensation but is less formal.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/queue Version ^8.0|^9.0 | — | — |
illuminate/support Version ^8.0|^9.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.