Recent releases, a complete README, tests in the repository, and clear organization backing support the project. Maintenance has since stopped, and workflow controls have notable weaknesses that add adoption risk.
18%
Total Score
75
88
50
Packagist marks the entire package as abandoned and names kafka-bus/laravel-bridge as its replacement. Package-wide deprecation is a severe dependency risk even though the release itself is recent.
The repository recorded zero commits and zero active maintainers in the last 3 months. That recent inactivity is a maintenance concern for a package that integrates with several framework and messaging components.
No SECURITY.md or equivalent security policy was found in the repository. This reduces transparency for reporting and handling dependency issues.
All 12 analyzed action references are unpinned, and the audit found a high-confidence bot-conditions issue in the Dependabot auto-merge workflow; two workflows also grant top-level write access. The pull_request_target trigger has no untrusted checkout or script-injection sink, so these are workflow hygiene concerns rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
micromus/kafka-bus Version ^1.1.1 | — | — |
illuminate/contracts Version ^10.0 || ^11.0 || ^12.0 | — | — |
micromus/kafka-bus-commiter Version ^1.1 | — | — |
micromus/kafka-bus-messages 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.