Will It Vibe?RBAC rule allows all API groups
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A Role or ClusterRole lists apiGroups: ["*"], so the rule spans every API group including RBAC and admission resources.
Why it matters
apiGroups: ["*"] makes an RBAC rule span every API group, including sensitive ones like rbac.authorization.k8s.io and admissionregistration. A rule that broad can let a compromised subject touch cluster security configuration it should never see. Naming the groups keeps the grant contained.
How to fix it
Replace apiGroups: ["*"] with the specific groups the workload uses, such as [""] for core resources or ["apps"] for Deployments. List each group the subject needs and no others. Review whether the rule still needs its verbs and resources narrowed as well.
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