- Is pbweb/buzz-bundle compatible with Laravel?
- No. pbweb/buzz-bundle is a Symfony bundle, and Laravel does not load Symfony bundles; its bundle registration, services.yaml, and Configuration tree have no analogue in Laravel's service provider model. For outbound HTTP in Laravel, use the Http facade or Guzzle directly.
- Is pbweb/buzz-bundle abandoned?
- Yes. The package description explicitly says ABANDONED, use symfony/http-client instead, and the underlying Buzz client is inactive and superseded by HTTPlug, PSR-18, and Symfony HttpClient. With no maintainer activity there is no CVE response path for an HTTP client that handles credentials, cookies, and TLS.
- How do I install pbweb/buzz-bundle?
- Run composer require pbweb/buzz-bundle, but only inside a Symfony app that registers the bundle. Expect dependency constraints pinned to EOL PHP and Symfony majors, so verify with composer why-not against your target runtime before any spike. Installability is not the same as working on your current runtime.
- What should I use instead of pbweb/buzz-bundle in Laravel?
- Use Laravel's Http facade, which wraps Guzzle and supports middleware, retries, auth, timeouts, and testing fakes. For lower-level control, use guzzlehttp/guzzle directly or a PSR-18 client implementation. Do not adopt Buzz in a Laravel app.
- What Symfony versions does pbweb/buzz-bundle support?
- The bundle's constraints are likely tied to old Symfony majors and either sensio/buzz or kriswallsmith/buzz, with no evidence of Symfony 6 or 7 support. PHP 8.2+ typing and Symfony deprecations will likely break it, and there is no upstream to fix it. Run composer why-not against your target PHP and Symfony versions first.
- Does pbweb/buzz-bundle support PSR-18 or PSR-7?
- Buzz predates PSR-18, so the bundle does not expose a modern PSR-18 client contract. It may use an older PSR-7 implementation internally, but that is not equivalent to PSR-18 interoperability. Symfony HttpClient is the first-party PSR-18-compatible answer.
- Can I configure timeouts, headers, and middleware in pbweb/buzz-bundle?
- Yes, in Symfony the bundle exposes YAML configuration for timeouts, headers, and middleware and registers configured client services. That is its stated integration purpose, plus a web-profiler panel for outgoing requests. In Laravel you would configure the Http facade or Guzzle instead.
- Is pbweb/buzz-bundle safe for production?
- High risk. An unmaintained HTTP client handles credentials, cookies, and TLS, and there is no CVE response path or field validation from downstream users. Treat "it installs" and "it works on our current runtime" as separate gates; neither is evidenced here.
- How do I migrate from Buzz to Symfony HttpClient or Guzzle?
- Define a thin internal HttpClientInterface or adopt PSR-18 as your contract, then implement it with Symfony HttpClient or Guzzle. Wrap legacy Buzz call sites behind the same contract so they migrate incrementally, then delete the Buzz wrapper. This avoids leaking bundle-specific types into domain code and gives you an exit ramp.
- What is the maintenance and bus factor of pbweb/buzz-bundle?
- Effectively self-maintenance from day one. The bundle has about 1 star, zero dependents, no visible release cadence, and no upstream maintainer to fix Symfony 6/7 or PHP 8.2+ breaks. If forced to adopt, vendor or fork it into an internal namespace, pin it, and open a ticket to remove it within two quarters.