olegstepura/sensio-buzz-profiler-bundle
Symfony bundle that adds a web profiler panel for the Buzz HTTP client, letting you inspect outgoing requests and responses during development. Useful for debugging third-party HTTP calls in older Symfony applications.
Category mismatch is the headline finding. Despite the framing, this is not a Laravel package. It is a Symfony bundle — it ships a Bundle subclass and a DI extension, relies on Symfony's container service IDs, and exists solely to bridge two other Symfony bundles (sensio/buzz-bundle and juliendidier/buzz-profiler-bundle). It provides no service provider, no config publish tag, no facade, and no Laravel-facing API. There is nothing to composer require into a Laravel application and nothing to register in config/app.php. The first TPM action is to correct the intake record, not to plan an integration.
Architecture fit: effectively zero. The package is thin glue — it wires a Buzz profiler data collector onto the default Buzz client service so the Symfony web profiler can display HTTP timing. Its entire value is bound to a stack we do not run: Symfony 2.x, the pre-Guzzle kriswallburg/buzz HTTP client, and the Symfony Profiler UI. Laravel's equivalents are Guzzle-based (Illuminate\Http\Client) and observed through Telescope, Debugbar, or Clockwork. There is no Buzz client in a Laravel app to profile, so the bundle has no attachment point.
Integration feasibility: negligible without a rewrite. Even if we wanted the behavior, the portable content is a handful of lines of middleware logic. Reimplementing it as a Guzzle middleware that emits timing data into Telescope is a small, self-contained task; adapting the bundle is not possible.
Technical risk: high if adopted, irrelevant in practice. The transitive dependency chain is abandoned end to end — Buzz itself, sensio/buzz-bundle, and the profiler bundle are all dead. Constraints will target PHP 5.x and Symfony 2.x, with PSR-0 autoloading that conflicts with modern PSR-4 tooling. No tests, no CI, single maintainer, 1 star, 0 dependents. The practical risk is not that it breaks production; it is that it consumes evaluation and legal-review cycles for something with no delivery value.
Key questions for the requester: (1) Is there any Buzz client anywhere in our portfolio, including legacy Symfony services? (2) What is the underlying need — HTTP client observability, or specifically Symfony profiler parity? (3) If it is observability, why is Telescope/Guzzle middleware insufficient? (4) Who added this to the candidate list, and against what requirement? The 0.005 score and 1-star/0-dependent profile suggest it surfaced from an automated scan rather than a human request; the 4.16 opportunity figure looks like a scoring artifact and should be discounted rather than treated as a signal.
Stack fit: none for Laravel; conditional for legacy Symfony. The only environment where this could run unmodified is a Symfony 2.0–2.3 application on PHP 5.3–5.6 that already has both parent bundles installed and still uses Buzz as its HTTP client. If we hold such an application, the bundle is a legitimate one-line convenience. If we do not — and we should confirm — there is no integration path.
Migration path: replace the intent, not the package. The equivalent capability in our stack is a Guzzle middleware registered on the Laravel HTTP client that records method, URI, duration, status, and payload size, then forwards to Telescope's watcher pipeline or a structured log channel. That is roughly a day of work, is testable, and carries no abandoned dependencies. Treat this package as a design reference for "attach a profiler collector to an HTTP client," not as code to install.
Compatibility: incompatible with PHP 8.x, Symfony 5/6/7, and Laravel 9/10/11 on every axis — language level, autoloading standard, container contract, and profiler API. Any attempt to modernize it is a fork, at which point we own it.
Sequencing, if we proceed at all:
Maintenance: we would inherit the entire upstream. No commits, no security patching, no PHP version bumps. Any fork becomes a permanent internal liability for a tool that only helps developers debug.
Support: no documentation beyond a README, no vendor, no community, no issue history worth citing. Support cost is effectively "we are the maintainers," which is a poor trade for a profiling convenience.
Scaling: not applicable in the usual sense. The Symfony profiler is dev-only by design; this never touches production traffic. Its scaling concern is the opposite — it does not scale to a stack it was not built for.
Failure modes are the quiet kind, which matters for tooling. The bundle works by matching specific service IDs in the container. When those IDs differ, it does not throw — the profiler panel simply stays empty. For an observability tool, silent no-op is the worst failure mode: engineers conclude "no HTTP calls were made" rather than "the collector is not wired." Secondary risks include PSR-0 class-resolution failures on modern autoloaders and constraint conflicts that block unrelated Composer upgrades.
Ramp-up: near zero to read, because the code is tiny, and near zero payoff. The transferable value is conceptual — how a profiler collector hooks an HTTP client — which is worth ten minutes of a senior engineer's time, not a dependency.
Recommendation: reject for adoption, close the intake, and redirect the underlying observability need to a native Guzzle/Telescope middleware. The one genuinely useful output of this evaluation is a confirmed inventory check on whether any Buzz clients remain in legacy Symfony services — that answer determines whether this is a non-issue or a modernization backlog item.
How can I help you explore Laravel packages today?