No health-check endpoint
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
No conventional health-check route was found, which most hosting/orchestration platforms rely on for liveness checks.
Why it matters
Load balancers, container platforms, and uptime monitors decide whether your app is alive by polling a known endpoint. Without one, they fall back to TCP checks that pass while the app is actually broken, and deploys cannot confirm the new version came up. A few lines makes outages visible instead of silent.
How to fix it
Add a GET /health route that responds 200 with a small JSON body like { ok: true }, registered before auth middleware so monitors can reach it. Keep it cheap and dependency-free; if you want a deeper readiness check such as a database ping, put that on a separate /health/ready path so a slow dependency does not flap liveness. Point your host’s health-check setting at the new path.
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