Monitor currently running jobs in Laravel Horizon for distributed systems
63%
Total Score
50
100
94
75
Only one registry account has publish access. That is a modest bus-factor concern for an independently owned package, although registry access alone does not establish actual maintenance activity.
No commits and no active maintainers were observed during the last three months, which weakens confidence that issues will be addressed promptly despite the recent release history.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-process gap for a package that includes web routes and job-control functionality.
The repository has no security policy, so there is no documented channel or process for reporting and handling vulnerabilities.
No GitHub Actions workflows were present, so there are no workflow findings; this also means the repository provides no observed CI or automated release-security practice to offset the tooling gaps.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/horizon Version ^5.0 || ^6.0 | — | — |
illuminate/redis Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/console Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/support Version ^9.0 || ^10.0 || ^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.