- What is misd/raven-bundle used for?
- The supplied overview describes it as a Symfony bundle that integrates the Raven PHP client so exceptions, logged errors, and custom events are reported to Sentry. It auto-registers a configured Raven client, adds a kernel listener for uncaught exceptions, and provides a Monolog handler. However, the technical assessment flags the package identity as contradictory, so verify the source before relying on either use case.
- Can I install misd/raven-bundle in a Laravel application?
- No, not as a normal Composer dependency. It is a Symfony 2 bundle registered through AppKernel and wired into Symfony's dependency injection container, and Laravel has no equivalent bundle extension surface. You would need an owned adapter or a different, Laravel-specific package.
- Does misd/raven-bundle support Laravel 9, 10, or 11?
- It does not support modern Laravel versions. The assessment describes it as Symfony 2.x and PHP 5-era code, and Composer will likely refuse resolution against PHP 8.x and Laravel 9 or newer. Forcing --ignore-platform-reqs on authentication or error-reporting code is not an acceptable production mitigation.
- How do I configure the Sentry DSN with misd/raven-bundle?
- According to the overview, configuration is done through YAML, including the DSN and Raven client options, and the bundle registers the configured client as a container service. Environment, release, and user-context tagging are also described as supported. Because the metadata is flagged as inconsistent, confirm the actual configuration keys in the source before use.
- How does misd/raven-bundle capture exceptions and logged errors?
- The described Sentry integration captures uncaught exceptions through a Symfony kernel listener and routes logged errors through a Monolog handler. This avoids boilerplate by wiring Raven into the framework container. The assessment warns that the README should be treated as untrustworthy until the repository is reviewed.
- Is misd/raven-bundle maintained and safe for production?
- The assessment rates technical risk as high. It cites one star, zero dependents, no visible CI on current PHP, a single-organisation maintainer, no security advisories, and a documentation identity mismatch. Signature verification and replay protection are security-sensitive paths that can rot silently when unpatched, so do not adopt it without source-level review.
- What are the alternatives to misd/raven-bundle for Sentry in Laravel?
- For Sentry error tracking in Laravel, use the maintained sentry/sentry-laravel package or the official Sentry PHP SDK with a Monolog handler. If the real requirement is Cambridge Raven or institutional SSO, the assessment recommends a maintained SAML or UCam WebAuth library such as SimpleSAMLphp, onelogin/php-saml, or LightSAML behind a custom Laravel guard.
- Does misd/raven-bundle work with Symfony 5, 6, or 7?
- No, the assessment identifies it as a Symfony 2 bundle that registers through AppKernel and old dependency injection patterns. It is not a drop-in for modern Symfony applications. Modern projects should use the current Sentry Symfony SDK or a maintained SSO library instead.
- How should I test an integration based on misd/raven-bundle?
- For the described Sentry path, test the container wiring and Monolog handler with a fake Raven client. If you are evaluating the repository's apparent WebAuth behaviour, use fixture-based automated tests plus a live test-IdP round trip, including negative cases for expired issue times, tampered signatures, and replayed parameters. The assessment notes no visible CI, so you must supply your own verification.
- Why does the description mention Sentry when the repository appears to be Cambridge Raven WebAuth?
- The technical assessment explicitly flags this as a documentation integrity issue: the supplied description contradicts the package's apparent identity and other sources. Either the metadata is mismatched or the repository was repurposed. Treat the README as untrustworthy, require source-level review before any build-versus-buy decision, and log the discrepancy as evidence that no maintained documentation contract exists.