- Is simonetti/ping-bundle a Laravel package?
- No. It is a Symfony bundle, indicated by the -bundle naming convention and Symfony bundle architecture, while Laravel packages integrate through service providers, facades, and the container. Treat it as Symfony-only until its composer.json proves otherwise.
- Can I use simonetti/ping-bundle in a Laravel 10 or 11 app?
- It is a poor fit for Laravel 10 or 11. Adoption would mean pulling Symfony HTTP kernel dependencies and hand-rolling bootstrap that Laravel does not provide for bundles. The recommended path is to reimplement a simple /health or /-/ping route natively or use a maintained Laravel health package.
- What does the ping endpoint actually check?
- The provided context does not confirm whether it returns a static HTTP 200 or performs readiness probes such as database, Redis, queue, or disk checks. That distinction changes operational risk significantly. Read the bundle class and controller or middleware before relying on it.
- How do I install simonetti/ping-bundle in Symfony?
- The intended path is composer require simonetti/ping-bundle and registration in bundles.php. First verify that its PHP and Symfony version constraints intersect with your application. If constraints do not match, do not force the install.
- Which Symfony and PHP versions does it support?
- The context does not verify supported versions; you must read composer.json for the PHP floor and Symfony major-version constraint. If it targets Symfony 4 or 5, those upstream versions are EOL and should not be adopted. Confirm PSR-4 autoload namespace and dependency conflicts before deciding.
- Is simonetti/ping-bundle safe for production?
- It carries high technical risk: one star, zero dependents, a composite score of 0.135, and no downstream production validation. The last release noted is 2024-01-29, with no releases in roughly two years and a bus factor of one. Adopt only after source review and with a plan to own the fork if maintenance stops.
- Does the ping endpoint include authentication or rate limiting?
- Authentication and rate limiting are not documented in the provided context. Health endpoints are often left unauthenticated, so you must inspect the controller or middleware for access controls. Also check whether it leaks version or build information.
- Is simonetti/ping-bundle actively maintained?
- There is no evidence of an active release cadence. The last release is dated 2024-01-29, the maintainer is a small org, and issue or PR latency is not confirmed. Check responsiveness before depending on it.
- What should Laravel developers use instead of this bundle?
- Laravel developers should implement a native /health or /-/ping route with a thin controller and an explicit HealthCheck service. For anything beyond a static 200, use a maintained Laravel health package with real adoption. Do not install this Symfony bundle in a Laravel application.
- How can I evaluate simonetti/ping-bundle before adopting it?
- Spend 30 to 60 minutes reading composer.json, the bundle class, and the controller or middleware. Gate adoption on framework and PHP compatibility, probe behavior, auth and rate limiting, and information leakage. Run it in staging and add tests for the exact health contract you need.