Weave Code
Status Bundle Laravel Package
markup/status-bundle
A lightweight PHP bundle for exposing and managing application status. Integrates cleanly with your framework to report health and runtime state through simple configuration. Useful for monitoring endpoints, status pages, and quick operational checks.
Markup Status Bundle
Frequently asked questions about Status Bundle
- Is markup/status-bundle compatible with Laravel?
- No, markup/status-bundle is not a Laravel package in any practical sense. Its name follows Symfony's bundle convention, and Laravel dropped bundle support at 5.0 in 2015. The last release in July 2017 predates Laravel package auto-discovery, so it will not autoload a service provider into a Laravel 10 or 11 application without a custom bridge.
- How do I install markup/status-bundle in a Laravel app?
- You can run composer require markup/status-bundle, but that does not make it a working Laravel integration. There is no Laravel service provider or auto-discovery entry, and the package's 2017 constraints will likely conflict with Laravel 8 through 11. Treat installation as a fork-and-patch exercise only, not a clean dependency.
- Which Laravel and PHP versions does markup/status-bundle support?
- The package has no stated Laravel version support and was last released in July 2017. That timeframe aligns with Laravel 5.x, not Laravel 8, 9, 10, or 11. Its PHP constraints are also likely to fail on PHP 8.2 due to removed functions and deprecation warnings.
- Is markup/status-bundle a Symfony bundle or a Laravel package?
- The Bundle suffix and the usemarkup repository strongly suggest a Symfony bundle, not a Laravel package. Laravel never used bundle terminology after 5.0. If it is a Symfony bundle, it will not integrate with Laravel's service container without a custom bridge that you would own and maintain.
- What does markup/status-bundle actually do?
- It exposes application health and status information through a single configurable endpoint and returns JSON. The advertised features include pluggable checks for databases, caches, and custom services plus aggregated healthy or unhealthy reporting. In practice that is a thin status surface that is straightforward to implement first-party.
- Is markup/status-bundle abandoned or still maintained?
- Yes, treat it as abandoned for planning purposes. The last release was July 2017, there are no dependents or meaningful community validation, and there is no active release cadence for security patches. Composer will likely flag it as abandoned or unmaintained.
- Can I use markup/status-bundle on Laravel 11 and PHP 8.2?
- It is not suitable for Laravel 11 on PHP 8.2. A 2017-era package typically trips dynamic-property deprecations, removed functions, and framework API changes long before it returns a health payload. Even on legacy Laravel 5.x you would be importing an end-of-life dependency into an end-of-life application.
- What are good alternatives to markup/status-bundle for Laravel health checks?
- For Laravel, prefer a maintained health-check package with active releases and dependents, or build the endpoint in-house. The required capability is small: liveness, database reachability, cache reachability, and a build identifier behind an auth token or network allowlist. That is typically less than a day of work including tests, with no upstream abandonment risk.
- How do I build a health check endpoint in Laravel without this package?
- Add a first-party route such as /health and a controller that returns a minimal JSON contract. Check application liveness, database connectivity, cache connectivity, and a version or build identifier, and gate the route with a token or IP allowlist. Keep the response free of PHP versions, dependency versions, connection strings, and queue depths to avoid information disclosure.
- Is markup/status-bundle safe to expose in production?
- No, exposing this package's status endpoint in production carries avoidable risk. Health endpoints are a classic information-disclosure vector for PHP versions, dependency versions, database connectivity, and queue depths, and this package has no reviewer community or release cadence to catch problems. Use a first-party endpoint with a strict response schema and access controls instead.
Weaver
How can I help you explore Laravel packages today?