Will It Vibe?hostNetwork enabled
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
hostNetwork: true places the pod on the node network namespace, bypassing NetworkPolicy and exposing host interfaces.
Why it matters
hostNetwork: true puts the pod directly on the node network stack. The pod then bypasses NetworkPolicy entirely, can bind and sniff host interfaces, and can reach services that were only meant to be node-local. It also creates port conflicts between pods on the same node.
How to fix it
Remove hostNetwork: true and expose the workload through a normal Service (ClusterIP, NodePort, or LoadBalancer) instead. The rare legitimate uses are node-level agents such as CNI or monitoring daemons; if this is one of those, keep it but constrain the pod with a tight securityContext and confirm it really needs host networking.
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