Weave Code
Actuator Bundle Laravel Package
symsensor/actuator-bundle
A Symfony bundle that adds actuator-style endpoints for application health, info, and runtime diagnostics. Configure readiness/liveness checks and expose operational status for monitoring and deployment workflows.
Inspired by Spring Actuator which provides an health probe endpoints for symfony applications.
Frequently asked questions about Actuator Bundle
- Can I use symsensor/actuator-bundle in a Laravel application?
- No. symsensor/actuator-bundle is a Symfony bundle built around kernel event listeners, DI service tags, compiler passes, and bundle registration, none of which exist in Laravel. Composer may install it into a Laravel 11 or 12 app after the v1.1.0 Symfony 7 constraint update, but the bundle will not register endpoints in Illuminate\Container. For Laravel, use the native /up route or spatie/laravel-health instead.
- How do I install symsensor/actuator-bundle with Composer?
- In a Symfony app, run composer require symsensor/actuator-bundle and enable the bundle in config/bundles.php, then configure exposed endpoints and paths. The package is not a Laravel package, so running the same command in Laravel will not produce working actuator routes. Check the declared PHP floor and Symfony constraint in composer.json before installing, because the exact PHP minimum is not confirmed in the public material.
- Which Symfony and PHP versions does symsensor/actuator-bundle support?
- v1.1.0 adds a declared Symfony 7.0 compatibility change following PR #1, so the earlier Laravel 11/12 Composer conflict with Symfony 7 constraints is likely resolved. The exact PHP version floor is still not clearly confirmed, and it is unclear whether the Symfony 7 path was tested or only had the version constraint widened. Treat a constraint bump without CI proof as a claim rather than a guarantee.
- Does the Symfony 7 compatibility release include tests and CI coverage?
- There is no clear evidence that the Symfony 7 compatibility change in v1.1.0 includes test or CI updates; the release appears to be a version-constraint edit only. Since the project has one star, zero dependents, and only two releases, there is no visible production test evidence either. Read the PR diff and CI configuration in the repository to confirm whether Symfony 7 is actually exercised.
- What is the difference between liveness and readiness endpoints in ActuatorBundle?
- The bundle advertises readiness and liveness endpoints intended for container orchestration, alongside health checks and structured JSON responses. The public material does not clearly confirm whether liveness and readiness are separate routes or a single aggregate endpoint, so verify this in the source before relying on it. This distinction matters because Kubernetes uses liveness to restart pods and readiness to remove them from load balancing.
- Is symsensor/actuator-bundle safe and production-ready?
- Treat it as high risk: one star, zero dependents, two releases, no security disclosure path, and no governance mean there is no production evidence. The v1.1.0 release shows an external contributor's PR was merged promptly, which is a weak positive signal of responsiveness, not a maintenance cadence. A dormant dependency in the health-probe path is especially dangerous because orchestration platforms use that path to decide whether to kill pods. Also verify whether checks are time-bounded, since a hung dependency could hang the probe and trigger restart loops.
- What Laravel alternatives should I use for health check endpoints instead?
- Laravel 11.x and later ship a native /up health route that is sufficient for most basic probes. spatie/laravel-health is a mature Laravel package with built-in checks, scheduling, and notifications. For simple needs, a custom controller or middleware returning JSON is easy to test and has no third-party provenance risk. Symfony Actuator Bundle is not a drop-in option for any of these.
- Can I port the health-contributor contract from ActuatorBundle to Laravel?
- Possibly, but only the domain layer is likely transferable: the health-contributor contract, status aggregator, and serializing controller. Contributor discovery in the bundle depends on Symfony DI service tags and compiler passes, so the first task is reading the source to see whether the contract itself is container-agnostic. If it is, a Laravel port is a modest reference reimplementation; if not, it becomes a from-scratch design. That question is unanswered and is the highest-value thing to check.
- Does symsensor/actuator-bundle expose environment details or exception traces?
- The public material does not answer whether response payloads expose environment details, configuration values, or exception traces. Probe endpoints are frequently unauthenticated and reachable from the cluster network, so detail leakage is a real security finding rather than a theoretical one. Review the serializing controller and every indicator's output before exposing the endpoint beyond localhost. Prefer returning only status codes and coarse check names in production.
- Does ActuatorBundle include authentication, IP allow-listing, or rate limiting?
- There is no evidence in the available material that the bundle includes authentication, IP allow-listing, or rate limiting for its endpoints. Plan to enforce access control at the web server, reverse proxy, or network policy layer, and bind probe routes to internal interfaces only. If you need application-level auth, you would have to add it yourself, which increases the maintenance burden on a low-activity dependency.
Weaver
How can I help you explore Laravel packages today?