- Can I use briareos/php-airbrake-bundle in a Laravel application?
- No. briareos/php-airbrake-bundle is a Symfony2 bundle and does not ship a Laravel service provider, config bridge, or modern framework integration. Laravel teams should use a Laravel-specific error reporter or a maintained SDK instead.
- Which Symfony and PHP versions does this Airbrake bundle support?
- It targets Symfony 2.x and relies on the legacy php-airbrake notifier, which is tied to PHP 5.x and early 7.x. It has no support for Symfony 3.4+ Flex, Symfony 4, 5, or 6. Composer installs on modern PHP runtimes will likely fail on platform constraints.
- How do I install briareos/php-airbrake-bundle?
- In a legacy Symfony2 application, install it with Composer, register the bundle in AppKernel, and add the bundle configuration for your Airbrake project. Expect dependency resolution to fail on modern PHP or Symfony versions. This is not a drop-in install for current frameworks.
- How is the Airbrake client configured in this bundle?
- The bundle exposes Airbrake settings through Symfony container configuration, using briareos_php_airbrake-style keys. You typically configure project credentials and environment-aware reporting there, and the bundle registers the Airbrake client as a service. Check the bundle's config for exact key names because it is a thin wrapper around php-airbrake.
- Does this bundle support Airbrake's current v3 or v5 notifier API?
- No. It wraps the legacy php-airbrake client and does not track Airbrake's v3 or v5 notifier API. Airbrake has moved its notifier APIs forward and de-emphasized its PHP SDK. That makes this bundle a poor fit for current Airbrake integrations.
- What are the production risks of using this bundle?
- The stack is end-of-life: Symfony 2.x and PHP 5.x no longer receive security patches, and the bundle cannot receive fixes. Error reporting is synchronous, so if the notifier throws inside the exception handler you can get masked failures or fatal recursion. Zero dependents also means the code has had no downstream scrutiny at scale.
- Is briareos/php-airbrake-bundle maintained or safe to depend on?
- Treat it as unmaintained. The package has a score of 0 with zero stars and zero dependents, a single author, and no release cadence or meaningful CI/test signal. Supply chain and vendor risk are high, especially because the underlying Airbrake PHP client is legacy.
- What alternatives should I use for error reporting instead?
- For modern Symfony, use maintained integrations such as sentry/sentry-symfony, bugsnag/bugsnag-symfony, Honeybadger's PHP client, or Rollbar. For Laravel, use the vendor's Laravel package or a maintained SDK rather than this Symfony2 bundle. Abstract reporting behind your own ErrorReporterInterface so the transport remains swappable.
- How should I integrate it in a legacy Symfony2 app?
- Only consider it for a maintenance-mode Symfony2 service where Airbrake is already the incumbent vendor and the app has a short end-of-life horizon. Register the bundle's client behind an application-owned ErrorReporterInterface::report(Throwable $e, array $context) seam. Treat it as a stopgap and plan to replace the transport with a maintained notifier.
- Can I test this bundle's error reporting in CI?
- The package has no meaningful public test or CI signal, so you must add your own integration tests around the reporting seam. Use a fake or stub reporter in CI and avoid real Airbrake calls. Also test failure behavior to ensure the notifier cannot throw inside the exception handler and cause recursion.