Redis-backed fair queue scheduling for multi-tenant Laravel applications
62%
Total Score
caution
A first v0.1.0 release has no maintenance track record, and both CI actions are unpinned.
This is the first registry release, published 0 days ago, so there is no release cadence or maintenance track record yet. Its age explains the gap but does not remove the uncertainty.
There were 0 commits and 0 active maintainers in the last 3 months, but the package itself is 0 days old. This limits evidence of ongoing maintenance rather than proving abandonment.
The repository has 0 stars, forks, and watchers, so there is no community adoption evidence yet. Because the package was released 0 days ago, this is better treated as limited evidence than as a standalone health failure.
Composer build tooling is present, but no security scanning tools were detected. For a new package, that is a modest transparency and hygiene gap.
The repository has no security policy. That weakens the documented process for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
illuminate/queue Version ^11.0|^12.0|^13.0 | — | — |
illuminate/redis Version ^11.0|^12.0|^13.0 | — | — |
illuminate/events Version ^11.0|^12.0|^13.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.