Will It Vibe?Host root filesystem mounted into a container
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
Bind-mounting the host root (/) into a container exposes every file on the host, including credentials and other containers, and read-write access is a direct path to host takeover.
Why it matters
Bind-mounting the host root (/) gives the container read, and often write, access to every file on the host: other containers, SSH keys, the Docker data directory, and system binaries. A write-capable root mount is a direct path to full host takeover. Even read-only, it leaks every secret on the machine.
How to fix it
Remove the root mount and bind only the specific directory the service needs, using the narrowest path and :ro when write access is not required. If the goal is host monitoring, use a purpose-built tool with a scoped, read-only mount of just the paths it reads. Never mount / into an application container.
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