- Is dbtlr/php-airbrake still maintained?
- No. The README opens with Deprecated, and the maintainer says he has not used Airbrake in roughly four years and lacks the time or desire to maintain the package. The last release was 2018-06-18, and he redirects new projects to the official airbrake/phpbrake package.
- How do I install dbtlr/php-airbrake in a Laravel app?
- Install it with composer require dbtlr/php-airbrake ~1.1 and require the generated vendor/autoload.php. It ships no Laravel service provider, facade, container bindings, or config publishing, so you must bind a configured notifier yourself. Treat it as a third-party SDK rather than a framework citizen.
- Does dbtlr/php-airbrake support Laravel 10 or 11?
- There is no Laravel version support to speak of. It is a framework-agnostic PHP 5.3 library that predates modern Laravel conventions and has no integration with Laravel's exception pipeline. It can sit alongside a modern Laravel app only through custom glue that you own and maintain.
- How do I wire dbtlr/php-airbrake into Laravel's exception handler?
- Laravel reports exceptions through Illuminate\Contracts\Debug\ExceptionHandler, Handler::report(), and the report() helper. To use this library you bind a configured notifier singleton in a service provider and call it from a custom handler, respecting $dontReport and filtering sensitive parameters. That glue is roughly one to two engineer-days of work you then own.
- Which Airbrake API version does dbtlr/php-airbrake use?
- It targets the Airbrake v2 notifier API. Airbrake has moved new projects onto a newer notifier protocol, and account-level configuration determines which endpoint will actually accept reports. The highest-severity risk is an error reporter that silently 404s while the team believes it has coverage, so send a live end-to-end test report.
- Does dbtlr/php-airbrake work on PHP 8.2 or 8.3?
- There are no compatibility commitments for PHP 8.2, 8.3, or 8.4. The code is from the PHP 5.3 era, with dynamic properties and untyped internals that can trigger deprecations. Verify it installs under your Composer constraints without --ignore-platform-reqs before depending on it.
- What are the best alternatives to dbtlr/php-airbrake for Laravel?
- For Airbrake specifically, use the official airbrake/phpbrake package. If Airbrake is a historical default rather than a contractual requirement, compare Sentry (sentry/sentry-laravel), Flare, and Bugsnag, all of which ship first-party Laravel packages. Unlike this library, those alternatives are actively maintained.
- Is dbtlr/php-airbrake safe to use in production?
- It is risky. The notifier makes synchronous outbound HTTPS calls from inside exception handling with no queueing, sampling, or circuit-breaking, which fails badly under error storms. It also has a single caretaker maintainer, no CVE monitoring, and dead CI, so production use means explicitly accepting that risk.
- How can I test that dbtlr/php-airbrake is actually reporting errors?
- The Travis CI and HHVM badges are obsolete and there is no meaningful automated verification of the code today. At minimum, send a live test report end-to-end this quarter and confirm your Airbrake account accepts the v2 endpoint. Also verify that sensitive request parameters are filtered before they leave the app.
- Can I swap dbtlr/php-airbrake for airbrake/phpbrake?
- Yes, and that is the recommended path for both new and existing projects. The API surface here is small, but the official package is different, so you will rewrite the configuration and exception-handler glue. Both the maintainer and Airbrake point you to airbrake/phpbrake.