Will It Vibe?No liveness probe
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
A long-running workload defines no livenessProbe, so Kubernetes cannot detect a hung process and restart it, leaving dead pods serving traffic.
Why it matters
A long-running workload with no livenessProbe cannot be automatically restarted when its process hangs or deadlocks. The pod stays Running while serving errors or nothing at all, and traffic keeps arriving until someone notices manually. A liveness probe lets Kubernetes recover the pod on its own. This is a heuristic scoped to long-running workloads.
How to fix it
Add a livenessProbe that reflects real health, typically an httpGet on a lightweight health endpoint or an exec/tcpSocket check. Set initialDelaySeconds so slow starts are not killed prematurely, and keep the probe cheap so it does not add load. Make sure the health endpoint checks liveness, not deep dependencies, to avoid restart loops.
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