Laminas Developer Tools Laravel Package

Product Decisions This Supports

• Framework-fit triage (the gating decision): this is a debugging module for Laminas MVC (formerly Zend Framework), not a Laravel package. It hooks into the Laminas MVC event lifecycle via EventManager, so it does not drop into a Laravel application. The primary PM decision it informs is where in the portfolio it belongs — legacy Laminas services, not the Laravel platform standard.
• Legacy estate / migration roadmap: if you maintain Laminas or Zend-derived apps alongside Laravel, this gives per-request baselines (query counts, timing, memory) you can capture before and after a rewrite. That makes "is the Laravel replacement actually faster?" a measurable question rather than a vibes question.
• Build vs buy for developer observability: on Laravel the buy answer is already Laravel Debugbar / Telescope / Clockwork. This package is then valuable as a requirements reference — it defines a credible minimum feature set (toolbar overlay, time/memory, SQL from the DB adapter, event collection, per-request report view) you can hold internal tooling against.
• Collector-pattern input for internal platform APIs: the EventManager-driven custom collector extension point is a reusable design idea if you're exposing domain-specific debug metrics (queue depth, cache hit rate, external API latency) from your own packages.
• Dependency governance policy: it is a dev-only diagnostic. PM owns the rule that it is excluded from production autoloads and never exposed on public-facing environments, alongside a security review of any toolbar that renders request internals.
• Support-risk budgeting: 24 stars and a single-module maintenance cadence (last release 2024-12-29) means it is a "good enough, don't build a strategy on it" dependency — relevant when deciding how deeply to couple to it.

When to Consider This Package

Adopt when:

• You genuinely run Laminas MVC applications (or Zend Framework apps already migrated to Laminas) and want lightweight toolbar profiling without standing up Xdebug or a full APM.
• You need development/staging-only visibility into SQL issued through laminas-db adapters, with no appetite for a heavier debugger.
• Licensing and hygiene matter: BSD-3-Clause is permissive with no attribution burden beyond notice retention, and the project is actively released — low legal and abandonment friction.
• You want a low-integration-cost complement to Xdebug rather than a replacement.

Look elsewhere when:

• Laravel is the target stack. Use Debugbar, Telescope, or Clockwork. Integrating this package would require hand-building an MVC lifecycle bridge that does not exist — pure cost, no differentiated value.
• You only need query inspection — Laravel's query log or Debugbar covers it.
• You need production-safe profiling; that's OpenTelemetry/APM territory, not a toolbar.
• Your team has no Laminas familiarity: the EventManager integration model is a real learning curve for marginal benefit.
• You need vendor-backed SLAs or a large community for troubleshooting — 24 stars is thin.

Blunt read on the score: 5.8/10 overall with a 7.48 opportunity score is exactly what a framework-mismatched but well-scoped tool looks like. The opportunity isn't in adopting it for Laravel — it's in the gap it highlights in your legacy tooling.

How to Pitch It (Stakeholders)

To executives: A small, permissively licensed, actively maintained developer-diagnostics module. Zero license cost, zero production footprint, dev-only. Recommendation: do not add it to the Laravel platform standard — it's built for Laminas MVC and would require custom integration work for no unique payoff. Approve it narrowly for Laminas services still in the portfolio, and treat it as a bridge during migration, not a strategic dependency.

To engineering: It's a Laminas MVC profiling module — toolbar overlay, request timing and memory, SQL captured from laminas-db adapters, event-driven custom collectors, and a detailed per-request report view. In Laravel it does not drop in; you'd be building an MVC event bridge yourself, so the default is Debugbar or Telescope. Where we do run Laminas, adopt it in development only, keep it out of production autoloads, and use its collector model as the reference design for the custom metrics we want in our own packages.