- Is ftrrtf/rollbar-bundle a Laravel package?
- No. ftrrtf/rollbar-bundle is a Symfony2 bundle that integrates Rollbar error monitoring into Symfony applications, not Laravel. It registers FtrrtfRollbarBundle in the Symfony kernel and exposes an ftrrtf_rollbar configuration tree. Dropping it into Laravel would require Symfony components and a custom service-provider shim, which is more work than a native integration.
- Can I install ftrrtf/rollbar-bundle in a Laravel application?
- You should not. The package is built for Symfony's dependency injection container and Monolog wiring, and its Composer constraints pin PHP to 7.x-era versions and symfony/symfony to ~2.x, which will fail resolution in modern Laravel projects. Even if forced in, you would need to write a service provider shim and manage Symfony components manually. Use rollbar/rollbar-laravel or sentry/sentry-laravel instead.
- What Laravel versions does ftrrtf/rollbar-bundle support?
- None. The bundle has no Laravel support and is not designed for Laravel's exception handler or logging channels. It targets Symfony2 applications and was last released on 2018-05-18 before being archived. There is no Laravel version compatibility to evaluate.
- How do I integrate Rollbar with Laravel?
- Use a Laravel-native package such as rollbar/rollbar-laravel, which hooks into Laravel's exception handler and logging channel. Alternatively, use sentry/sentry-laravel if you are still choosing a vendor and prefer a first-party maintained SDK. Do not use a Symfony bundle for this purpose.
- Is ftrrtf/rollbar-bundle still maintained?
- No. The repository is archived and the last release was 2018-05-18. It has roughly 13 stars and zero Packagist dependents, which means there is no downstream validation or evidence of active production use. Archived packages receive no security patches, so treat it as unmaintained legacy code.
- What PHP and Symfony versions does ftrrtf/rollbar-bundle require?
- The Composer constraints almost certainly pin PHP to 7.x or earlier and symfony/symfony to ~2.x. Symfony 2.x reached end-of-life in November 2018, so any application still running it is itself unpatched. On PHP 8.x, Composer will refuse to resolve the package.
- How does ftrrtf/rollbar-bundle report exceptions and log messages?
- It is a thin wrapper over rollbar/rollbar-php that provides an exception listener, a Monolog handler, and a configuration definition. The listener catches exceptions in the Symfony request cycle, while the Monolog handler forwards log records to Rollbar. Reporting is synchronous in the request path, so latency and timeout exposure exist when Rollbar is unreachable.
- What are the production risks of using ftrrtf/rollbar-bundle?
- The main risks are unpatched transitive dependencies with no CVE response path, synchronous reporting that can add latency, and PII leakage because 2018-era defaults are unlikely to scrub request parameters and person data aggressively enough for GDPR or CCPA review. You can also get double-reporting if both the bundle's exception listener and a Monolog handler are active. These risks are why the package is deprecated.
- What are the best alternatives to ftrrtf/rollbar-bundle for Laravel?
- For Laravel, use rollbar/rollbar-laravel if Rollbar is your chosen vendor, or sentry/sentry-laravel if vendor selection is still open. Sentry generally wins on maintenance cadence and first-party Symfony and Laravel support. Both integrate with Laravel's exception handler and logging channels without Symfony bundle overhead.
- How do I migrate away from ftrrtf/rollbar-bundle?
- Inventory which applications actually depend on it; with zero Packagist dependents this is likely one or two internal repos. Freeze new adoption, choose an error-tracking vendor at the platform level, and replace the bundle with the vendor SDK directly, such as rollbar/rollbar-php with RollbarHandler or Sentry's Symfony bundle. Preserve access token, environment, and scrub/whitelist settings, validate capture parity in staging, then remove the dependency from composer.json so it cannot silently return.