- What does victord11/ssl-certification-health-check do?
- It is a single-purpose Laravel health check that performs an outbound TLS handshake against configured hosts and returns pass or fail based on certificate status. The overview says it covers expiry dates, validity, issuer, and chain issues, so it is intended for monitoring rather than certificate renewal or deployment. It fits Laravel applications that already expose a health endpoint or run scheduled diagnostics.
- How do I install victord11/ssl-certification-health-check in a Laravel app?
- Install it with Composer using composer require victord11/ssl-certification-health-check, then check whether the package supports Laravel package auto-discovery; if not, register its service provider manually. Publish any provided config file and list the domains you want to monitor. Then wire the check into your health-check runner, which in most Laravel apps means spatie/laravel-health or the framework health route. Confirm the exact dependency and registration steps in the package README and composer.json before rolling it out.
- Which Laravel and PHP versions does this SSL certificate check support?
- The package's last release was 2024-03-28, so it most plausibly targets the Laravel 10/11 and PHP 8.1+ era, but the provided material does not confirm exact constraints. Check composer.json for the required PHP version and the health-check framework constraint before installing. Pin the version you validate and test on your actual Laravel major version, because a future framework bump could strand the package.
- Does it check only certificate expiry or also the full chain and hostname match?
- The overview claims expiry, validity, issuer, and chain issues, but the technical assessment flags that you must verify whether that means full chain trust and hostname/SAN matching or expiry-only behavior. Read the Check class and its TLS verification options. This matters because an incomplete intermediate chain is a common real outage that expiry-only checks miss.
- Can I run the SSL check on a schedule instead of the HTTP health endpoint?
- Yes, the safer pattern is to run the check on a schedule, for example via a scheduled Artisan health command or a queued diagnostic, rather than inside a synchronous HTTP liveness route. Each check adds a full TLS handshake, roughly 50 to 500 ms and worse on timeout, so dozens of domains can turn a health endpoint into a latency liability. Cache or schedule results if the HTTP endpoint must stay fast.
- Why does the SSL certificate check fail in production but pass locally?
- Local environments usually have unrestricted outbound TCP/443 and DNS, while production containers may run in private subnets without NAT or behind egress filters. SNI handling and DNS resolution can also differ. If the check treats all failures as a generic unhealthy result, verify DNS failure, connection refusal, and timeout behavior separately so you do not chase false certificate alarms.
- Does it support custom ports, SNI overrides, and configurable timeouts?
- Support for custom ports, SNI overrides, and configurable timeouts is not confirmed in the provided material; inspect the published config and the Check implementation. A typical implementation performs an outbound TLS handshake to port 443 with whatever timeout the framework or stream context defaults provide. If your hosts use non-standard ports or need explicit SNI, confirm that the package exposes those options before adopting it.
- Does this package have tests and CI across multiple Laravel versions?
- A test suite and CI matrix across Laravel versions are important maintenance signals, but the assessment does not confirm either. Check the repository for a tests directory, a CI workflow, and whether it runs against multiple Laravel majors. If there is no test coverage, treat the package as fork-ready code and add your own integration test against a known certificate.
- Is it safe to depend on a Laravel package with 17 stars and a 2024 release?
- It is MIT licensed, small, and low blast radius, so fork-and-vendor is a legitimate fallback, but 17 stars and a last release in March 2024 are weak maintenance signals. Pin the version, keep the check isolated behind your health-check abstraction, and be ready to replace it with a custom check. The integration risk is bounded mainly because the package is cheap to replicate.
- How does this compare to spatie/laravel-health or external SSL monitoring?
- spatie/laravel-health is the broader health-check registry; this package is one SSL-specific check that likely plugs into such a runner. External monitoring services cover certificate expiry from outside your network and can alert independently of your application. This package does not renew, rotate, or deploy certificates, so compare it as a diagnostic probe, not a certificate-management tool.