Airbrake Bundle Laravel Package

Product Decisions This Supports

• Error monitoring vendor evaluation. If you are standardizing on Airbrake (or comparing it against Sentry, Bugsnag, Rollbar), this package remains a reference implementation of Airbrake's API v3 wire protocol — useful as a working example of how notice payloads, context, and environment data are shaped on the PHP side. The new 2.2.0 release upgrades the underlying phpbrake dependency to 0.5, but does not change the protocol reference value.
• Build-vs-buy for exception reporting. A small, readable integration like this is the "build" baseline: it shows roughly how much code a native Airbrake notifier costs. If you're weighing a paid SDK or maintaining in-house error plumbing, this sets the floor for effort.
• Legacy Symfony2 estate inventory. Relevant if you're mapping maintenance obligations across an older PHP/Symfony application portfolio and deciding which services get migrated, wrapped, or retired.
• Integration pattern guidance for internal tooling. Teams building their own Airbrake-compatible notifier (for a Laravel app, a queue worker, or a CLI) can still crib the bundle's structure for service container wiring, configuration, and error listener registration.

Important caveat for roadmap work: despite the Laravel/PHP framing, this is a Symfony2 bundle, not a Laravel package. It targets Symfony 2.x, which reached end-of-life in 2018. It should not appear on a Laravel error-monitoring roadmap at all; if the request originated there, that is a scoping error to correct before it becomes an engineering estimate. The 2.2.0 release does not change this: it is a dependency bump only, with no Symfony 4+/5+/6+ support and no PHP 8 compatibility claim.

When to Consider This Package

Consider it only when:

• You maintain a Symfony 2.x application that is already on Airbrake and you need a reference for the v3 API contract.
• You are doing archaeology — reading how a prior team integrated error reporting, to inform a migration to Sentry, a modern Airbrake SDK, or Symfony's native ErrorHandler/Monolog stack.
• You need a minimal protocol example for a throwaway internal script and are not shipping the code itself.

Look elsewhere when:

• You are on Laravel — use airbrake/airbrake-php with a Laravel service provider, or Sentry's first-party Laravel SDK.
• You need supported, maintained tooling. The 2.2.0 release only bumps phpbrake to 0.5; prior to that, the last release was December 2017. One star, zero dependents, and a score of 0.005 are still signals of abandonment: no security patches, no demonstrated PHP 8 compatibility path, and no Symfony 4+/5+/6+ support. A single dependency bump is not evidence of active maintenance.
• You need PHP 7.4+ or PHP 8.x runtime compatibility, modern autoloading conventions, PSR-3/PSR-18 alignment, or async/batched error delivery.
• You need vendor accountability — no SLA, no CVE response, no upstream issue triage.
• Your product has compliance or uptime commitments that require a supported dependency with a maintenance contract.

Verdict: treat this as documentation, not a dependency. Do not add it to a production dependency graph. The 2.2.0 phpbrake 0.5 bump does not change the recommendation.

How to Pitch It (Stakeholders)

For executives: This is a long-dormant, single-maintainer Symfony 2 integration for the Airbrake error-reporting service. It has essentially no adoption — one star, zero dependent packages — and had no release between December 2017 and a recent 2.2.0 dependency bump that only upgrades phpbrake to 0.5. It is not a candidate for adoption. Its only business value is as a reading reference while we decide how to consolidate error monitoring across our PHP estate. Recommend we not take on this dependency and instead budget a short evaluation between Airbrake's maintained SDK and Sentry for the legacy Symfony services we still run. That evaluation is roughly a one-sprint spike, and the outcome determines whether we migrate, wrap, or retire those services.

For engineering: Use this repository as a protocol reference only — it demonstrates Airbrake API v3 notice payload construction and Symfony service-container wiring. Do not install it. It targets an EOL framework (Symfony 2.x) and a 2017-era PHP toolchain, with no PHP 8 support and no security response. The 2.2.0 release only upgrades phpbrake to 0.5; treat it as a dependency refresh, not a modernization signal. If we need Airbrake on a current stack, evaluate airbrake/airbrake-php or the Sentry PHP/Laravel SDKs, both of which have active maintenance. If a ticket cites this package as a dependency for a Laravel service, the ticket is mis-scoped — flag it back to the requesting team before estimating.