Source code
Stability
Releases
No health / readiness endpoint
Part of the Observability gaps check · fix arrives as a draft
What it is
The service exposes no health or readiness endpoint for the platform to probe.
Why it matters
Without one the orchestrator or load balancer cannot tell a starting instance from a working one, so traffic arrives before the app is ready and keeps arriving after it has broken.
How to fix it
Expose a liveness endpoint that returns 200 when the process is running and a separate readiness endpoint that checks the dependencies it needs to serve traffic, then point the platform's probes at them.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.