Will It Vibe?Binding grants cluster-admin
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
A RoleBinding or ClusterRoleBinding references the built-in cluster-admin role, granting full read/write over every resource in scope.
Why it matters
Binding a subject to the built-in cluster-admin role grants full read and write over every resource in the cluster, including secrets, RBAC, and workloads in every namespace. If that subject is a service account or a broadly shared user, a single compromise becomes a full cluster compromise. Almost no workload needs this level of access.
How to fix it
Replace the cluster-admin reference with a Role or ClusterRole scoped to exactly the resources and verbs the subject needs. Prefer a namespaced RoleBinding over a ClusterRoleBinding where possible. Reserve cluster-admin for a small number of human break-glass accounts, not for automation.
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