Will It Vibe?No health-check endpoint
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
A real API surface exists but no route resembling /health, /healthz, /ping, /status, or /ready was found anywhere. Load balancers, container orchestrators, and uptime monitors need a cheap endpoint to check before routing traffic; without one, a stuck-but-listening process can keep receiving requests indefinitely. This is a heuristic: a serverless function behind a platform-managed health check may not need its own.
Why it matters
With a real API surface but no /health, /healthz, /ping, /status, or /ready route anywhere, there is no cheap endpoint for a load balancer, container orchestrator, or uptime monitor to poll before deciding whether to send traffic to this instance. Without one, a process that is technically still listening but stuck, out of memory, or unable to reach its database can keep receiving requests it will never successfully answer, and the operator finds out from user complaints instead of an automated check.
How to fix it
Add a lightweight route, typically GET /health or /healthz, that responds quickly with a 200 when the process can serve traffic and a non-200 when it cannot. Keep it cheap: checking that the process is up and, optionally, that its database connection is alive, is usually enough; avoid doing expensive work on every health check.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo