The project has tests, a clear README, an MIT license, and organizational ownership. Its small release burst, no commits in three months, and unpinned workflow actions leave maintenance and build-integrity concerns.
62%
Total Score
83
100
86
75
All five releases arrived on January 23, 2026, while the package has had no newer release over the following 237 days. This concentrated initial activity provides less evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the same-day release burst, this is a meaningful sign that maintenance may have stopped.
Composer build tooling is present, but no security-scanning tools are reported. That is a modest transparency gap, not a severe risk by itself.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it does not by itself show abandonment.
All three workflows were analyzed cleanly with no dangerous triggers, untrusted checkouts, or audit findings, and no top-level write permissions. However, all four action references are unpinned, leaving avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/queue Version ^11.0|^12.0 | — | — |
illuminate/console Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
infoesportes/messaging-rabbitmq Version ^1.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.