- Is lag/colonel-smoker-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package: there is no ServiceProvider, no config publish path, and no Illuminate contracts. Making it work in Laravel would require a bespoke adapter for Symfony's DI extension and CompilerPass model, event dispatcher, and HTTP kernel.
- What does Colonel Smoker actually do?
- The metadata describes it as handling 'the smoke' in an application, which most likely means smoke tests, health checks, or error surfacing. The repository does not make the exact behavior clear, and its differentiation is not evident from the available metadata. Confirm whether it is an in-process smoke-test harness or a client for a hosted service before considering it.
- How do I install lag/colonel-smoker-bundle?
- For Symfony, you would install it with Composer and register the bundle in your kernel. There is no documented Laravel installation path, and composer require in a Laravel app would not wire up service providers or configuration. Laravel teams should not treat it as a drop-in dependency.
- Does it support PHP 8 and current Symfony versions?
- The last release was 2019-11-15, roughly six years ago, and it is likely constrained to symfony/* ^3.4 or ^4.x and PHP ^7.1. It is three to four Symfony majors and three PHP majors behind current versions. Expect breakage on PHP 8 from container and extension API changes, EventDispatcherInterface signature changes, added return types, and removed container-aware base classes.
- Is it safe to use in production?
- Production use is high risk because the package is unmaintained, has three stars, zero dependents, and no security response process. If it runs in middleware or an exception handler, a failure there can mask the original error. If it transmits exception payloads off-host, that is also a legal and data-protection review item.
- What alternatives should Laravel developers use for smoke tests and health checks?
- Laravel already provides a /up health route, php artisan about, schedule:run heartbeats, and Horizon or Telescope for exception visibility. A pre-deploy smoke suite can be written as a handful of Pest or PHPUnit HTTP assertions in one to two days. That approach produces code you own and understand.
- Can I fork it and port it to Laravel?
- Only if the license permits it and discovery shows non-trivial logic you cannot cheaply reproduce. The license is not confirmed in the available metadata, so check the repository LICENSE first, and confirm whether the repo is archived or has a successor. A full port means Symfony-bundle-to-Laravel-package work, PHP 8 compatibility, tests from zero, and permanent ownership.
- Does it send application data off-host?
- That is not answered by the available metadata, and it is the key risk question. If the Colonel is a remote service, exception payloads would leave your estate, and with no maintainer there is no DPA counterparty, no security response, and no way to audit what is transmitted. Treat that as a legal review item, not just a technical one.
- Is the package still maintained?
- No active maintenance is evident: the last release was 2019-11-15, with three stars, zero dependents, and no issue history to mine. The repository may be archived or merely quiet, so check its status and whether the author has a successor package. Zero dependents also means nobody will file the issue that tells you it broke.
- What is the license and can I use it internally?
- The license is not confirmed in the available metadata, so verify the repository LICENSE before internal use or forking. If it is permissive, an internal fork is possible but carries the full porting and ownership cost. If it is unclear or restrictive, do not depend on it.