hostIPC 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
hostIPC: true shares the host IPC namespace, exposing shared memory of other processes on the node.
Why it matters
hostIPC: true shares the host inter-process communication namespace. The container can then access shared memory segments and semaphores belonging to other processes on the node, which can leak data between unrelated workloads or be used to interfere with them.
How to fix it
Remove hostIPC: true. Workloads that need to share memory should do so within their own pod, not with the host. Keep the setting only for specialized node agents that have a documented need, and constrain those pods accordingly.
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