Will It Vibe?Service has no restart policy
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
Without a restart policy a crashed or OOM-killed service stays down until someone notices, instead of recovering automatically. This is a best-practice heuristic; short-lived one-shot jobs may not need one.
Why it matters
Without a restart policy, a service that crashes, is OOM-killed, or exits on a transient error stays down until a human restarts it, turning a brief blip into an outage. In production you almost always want the container to come back automatically. This check is a best-practice heuristic and does not apply to short-lived one-shot jobs.
How to fix it
Add a restart policy to each long-running service: restart: unless-stopped is a good default for most services, or restart: on-failure to retry only on error exits. Under the deploy key you can use restart_policy with a condition and backoff. Leave one-shot jobs without a policy, or use restart: "no" to be explicit.
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