- Does gamma/api-logger-bundle work with Laravel?
- No. The package is a Symfony DI bundle: it registers through a Bundle class and hooks Symfony kernel events such as kernel.request and kernel.response, none of which fire inside Laravel's HTTP kernel. There is no service provider, no facade, and no Laravel config file. Treat it as Symfony-only unless an install spike proves otherwise.
- Can I require gamma/api-logger-bundle via Composer in a Laravel 10 or 11 app?
- Not reliably. With no release since July 2018, its composer.json most likely pins PHP 7.x, Symfony 3 or 4, and Guzzle 6, all of which conflict with Laravel 10/11 running on PHP 8.2 or 8.3. Installing with --ignore-platform-reqs is not a production strategy, because the Guzzle 6 to 7 ClientInterface change can break middleware silently or fatally. Fork and vendor instead.
- Is gamma/api-logger-bundle still maintained?
- There is no meaningful signal of maintenance. The last release was 2018-07-15, the repository has zero stars and zero dependents, and there is no public test or CI evidence. A Packagist score around 0.09 is consistent with a personal or experimental project rather than a production dependency. Any bug or vulnerability in it becomes permanently yours.
- Is gamma/api-logger-bundle compatible with PHP 8.2 and 8.3?
- Very unlikely without patching. Code from 2018 predates typed properties and union types, and constructs that were deprecations in PHP 7 became fatal errors in PHP 8.x. Expect untyped ArrayAccess return signatures, dynamic property deprecations, and possibly legacy functions like create_function or mcrypt to surface during a trial install.
- Does it log request bodies and headers by default, and can I redact secrets?
- The README does not say, so you must read the source before trusting it. A request and response logger that captures headers and payloads will pick up Authorization tokens, cookies, passwords, and PII unless there is an explicit redaction or allow-list mechanism. With no maintainer and no security-response process, that exposure is a GDPR and PCI question first and an engineering question second.
- Can I reuse its Guzzle middleware inside a Laravel application?
- That is the only realistic integration path, but it has to be confirmed by reading the source rather than the README. Laravel's Http facade is Guzzle-backed, so a framework-agnostic Guzzle middleware for outbound logging ports cleanly into a first-party package. If the logging core is tangled with Symfony's container and event dispatcher, there is nothing to lift.
- What Laravel packages already handle API request and response logging?
- Laravel Telescope and Clockwork cover request inspection out of the box, spatie/laravel-activitylog handles audit trails, and Guzzle log middleware or OpenTelemetry PHP cover outbound calls. All are free, maintained, and Laravel-native. Any adoption of this bundle has to beat them on effort and risk, which on current evidence it does not.
- How would I integrate gamma/api-logger-bundle into a Laravel project?
- Not with composer require. Fork it into an internal namespace, pin a specific commit SHA, and register it through a path or VCS repository so the dependency is immutable and reviewable. Then extract only the logging core and discard the Symfony bundle class, DI extension, and compiler passes. Build the service provider, configuration, and middleware yourself.
- Where does it write logs, and does it support sampling?
- Unknown from the one-line README, and both matter in production. You need to know whether it performs a synchronous database insert, a file append, or a queue push, and whether high-traffic endpoints can be sampled. Without sampling, a logger that captures bodies on every request becomes a latency and storage problem.
- Is there a tagged release, a test suite, and a permissive license?
- There is no evidence of tests or CI, and you may only be able to pin dev-master rather than a tagged version. Check the LICENSE file, because the fork-and-vendor work this requires is only legal if the license permits it. If any of those three is missing, budget for owning the code outright.