Will It Vibe?Resource pinned to the default namespace
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A manifest sets namespace: default, which mixes the workload with unrelated resources and prevents namespace-scoped quotas and policies from applying.
Why it matters
Pinning a resource to namespace: default drops it into the shared catch-all namespace alongside unrelated workloads. That makes access control, resource quotas, and network policies harder to apply cleanly, and it mixes environments that should be separated. Named namespaces keep workloads organized and independently governable. This is low severity.
How to fix it
Move the resource into a purpose-named namespace (for example team-payments or staging) and create that namespace if it does not exist. Manage the namespace value through Kustomize or Helm so environments stay separate. Apply per-namespace quotas and policies once workloads are grouped sensibly.
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