The project is small and clearly packaged, with a useful README and release notes for this version. Its one-person ownership, no commits for three months, and lack of security tooling or policy leave maintenance and oversight thin; pin this version rather than tracking it loosely.
57%
Total Score
50
100
88
67
Only one registry account has publish access. That is workable for a personal package but leaves limited publishing continuity if the maintainer becomes unavailable.
The package published 24 releases in an 18-day period, with a median interval of 0 days. This shows active initial iteration but not yet a proven long-term release pattern.
The repository recorded zero commits and zero active maintainers during the last three months. For a recently released package, that is a meaningful warning that maintenance may have stalled.
Composer build tooling is present, but no security-scanning tools were detected. This weakens automated oversight for a package handling application metrics and notifications.
The repository has no security policy. That makes vulnerability reporting and response expectations less transparent, especially for a package used in production Laravel applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/queue Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/redis Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/database Version ^9.0|^10.0|^11.0|^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.