Bus Laravel Package

Product Decisions This Supports

• Build vs. buy for command dispatch: This package exists to answer a question Laravel answered natively years ago. The decision it supports is not "adopt or not" but "do we carry a third-party bus abstraction or use the framework's Illuminate\Contracts\Bus\Dispatcher?" The default answer is the framework.
• Architecture patterns worth borrowing: Even as a dead dependency, it is a useful reference for middleware-pipelined command dispatch, self-handling commands, and command/query separation. Engineering can cite it when designing an internal dispatch layer without taking the dependency.
• Dependency risk register: Archived repo, zero dependents, last release July 2020, opportunity score 16.7 — this is a textbook entry in a "do not adopt / migrate off" list, and a useful calibration point for how we score the rest of the catalog.
• Legacy triage: If any service already depends on it, that is a roadmap item (migration to native bus), not a feature item.
• Roadmap: No investment. No fork, no sponsorship, no upstream contribution — there is no maintainer to accept it and no user base to justify it.

When to Consider This Package

• Only when maintaining an existing application that already has it in composer.json — and even then the decision is "scope the removal," not "upgrade."
• As a read-only architectural reference when writing an internal ADR on dispatch middleware, handler resolution, or command/query separation.
• As a teaching example of why framework-adjacent packages decay: the framework absorbed the feature set, the maintainers archived, and the release cadence stopped.

Look elsewhere when:

• Starting anything new. Use Laravel's native bus, queued jobs, and pipeline middleware — they cover the same ground with first-party support and security patching.
• You need an actively maintained, framework-agnostic bus: consider Symfony Messenger or League Tactician.
• You need long-term support, PHP 8.x guarantees, or a security response process. Archived = no CVE response, no compatibility fixes, no maintainer.
• You need ecosystem validation. Zero dependents is a strong negative signal for a package whose whole purpose is to be depended upon.

How to Pitch It (Stakeholders)

For executives: This is an archived, single-maintainer package last released in 2020, with no downstream dependents. Adopting it would add vendor risk for functionality Laravel already ships in core. Recommendation: do not adopt; budget zero. If any existing system depends on it, treat removal as small technical-debt work with a clear owner — the cost of staying is a permanent unpatched dependency, the cost of leaving is a refactor to the native bus.

For engineering: The underlying ideas are sound — middleware pipelines around command dispatch, self-handling commands — but Laravel's dispatcher and pipeline have covered this since 5.5, with queue integration, job middleware, and batching on top. Use the native bus. Reference this repo's source if you want a pattern to copy, not a library to depend on. Expected migration effort for a typical consumer is low-to-moderate: swap the dispatcher binding, move middleware onto the framework pipeline, delete the dependency.

Bottom line: Historically interesting, operationally dead. Zero adoption risk accepted, zero spend, one migration ticket if we find it in the wild.