Will It Vibe?Service has no resource limits
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 service with no CPU or memory limit can consume all host resources and starve its neighbours, turning one runaway container into a host-wide outage. This is a best-practice heuristic.
Why it matters
A service with no CPU or memory limit can consume everything on the host, so one runaway or memory-leaking container can starve every other service and take down the whole machine. Without a memory limit the kernel OOM killer may also kill an unrelated process instead of the offender. This check is a best-practice heuristic; some local development stacks intentionally skip limits.
How to fix it
Add resource limits to each long-running service. Under Compose use deploy.resources.limits with cpus and memory, or the mem_limit and cpus shorthand, sized from observed usage with some headroom. Set limits per service based on what it actually needs rather than a single global number.
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