Event Laravel Package

Product Decisions This Supports

• Event-driven decoupling inside the product: whether to introduce domain events, observer hooks, or a pub/sub layer for capabilities like audit trails, notification fan-out, webhook delivery, search indexing, and plugin/extension points. This package represents one implementation option on that spectrum.
• Build vs. buy vs. borrow: specifically the "borrow" branch — pulling a small, permissively licensed event broker instead of writing one in-house. The honest PM conclusion here is usually a fourth option: use the framework's own dispatcher, already paid for and already maintained.
• Dependency health policy calibration: a concrete worked example for your adoption rubric. Archived status, a 2017 last release, and zero dependents make it a useful reference case when setting standards for future package reviews and exceptions.
• Legacy modernization roadmap: if any service in the estate already uses Hoa\Event, it becomes a line item on the migration backlog — a known removal — rather than a candidate for new capability work.
• Prioritization input: integration cost is near zero (one Composer line), but carrying cost is non-zero and permanent. That asymmetry is the decision, not the feature.

When to Consider This Package

Consider it only when:

• You maintain a legacy PHP 5.x/7.x codebase already built on the Hoa stack and need consistency with sibling Hoa libraries that are still in use.
• You need a minimal, framework-agnostic broker with named listeners, listener priorities, and a bucket/data payload, and you are prepared to vendor the source and own it outright.
• You are evaluating event API ergonomics for an internal design — as reference material, not as a runtime dependency.

Look elsewhere when:

• You are on Laravel. Illuminate\Events\Dispatcher already covers listeners, subscribers, queued listeners, and broadcasting, and is maintained by the framework you are already supporting.
• You need PSR-14 compatibility. Hoa\Event predates it and will not interoperate with symfony/event-dispatcher, league/event, or psr/event-dispatcher.
• You need PHP 8.x support, typed signatures, or static analysis to pass. Archived repositories ship no compatibility guarantees.
• You need a security response path. There is no upstream to issue a patch, and no dependents to notice a break.
• You need async or queued delivery at scale. That is a queue and infrastructure decision, not a library decision.

Signals to weigh: 321 stars is modest for a foundational primitive; zero dependents means no inheritor community for bug fixes; the 2017 release date implies roughly eight years of unpatched drift against the PHP runtime.

How to Pitch It (Stakeholders)

For executives: Hoa\Event is a small, archived PHP event library. It is not a strategic dependency and should not enter the stack. We already own an equivalent capability in Laravel's event dispatcher at no additional licensing, support, or migration cost. Adopting it would add an unmaintained component with no security response path — a seemingly cheap decision now that becomes expensive at the next PHP upgrade or security review.

For engineering: It solves a real problem — decoupled listener dispatch with priorities and typed payload buckets — but with a bespoke pre-PSR-14 API, no PHP 8 guarantees, and no upstream. Recommendation: build against Illuminate\Events or PSR-14 interfaces so the implementation stays swappable. If we ever inherit Hoa code, wrap it behind our own dispatcher interface and schedule its removal rather than extending it.