Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
58 of your 226 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 55.04s for a 200.1 MB repo slow.
  • Repobility's analysis ran in 49.92s after the clone landed.

kubernetes/kubernetes

https://github.com/kubernetes/kubernetes · scanned 2026-06-05 05:10 UTC (10 hours, 50 minutes ago) · 10 languages

1074 findings (178 legacy + 896 scanner) 11/13 scanners ran 57th percentile · Go · huge (>500K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 10 hours, 50 minutes ago · v2 · 626 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 85.0 0.20 17.00
documentation_score 98.0 0.15 14.70
practices_score 42.0 0.15 6.30
code_quality 69.0 0.10 6.90
Overall 1.00 82.7
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 75 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… hack/verify-flags-underscore.py:42
  • medium Agent control bridge may listen on a network interface without visible auth pkg/proxy/apis/config/scheme/testdata/KubeProxyCo…:2
  • medium Agent control bridge may listen on a network interface without visible auth pkg/proxy/apis/config/scheme/testdata/KubeProxyCo…:2
  • medium Agent control bridge may listen on a network interface without visible auth cluster/gce/config-test.sh:13
  • medium Agent control bridge may listen on a network interface without visible auth cluster/gce/config-default.sh:13
  • medium Suspicious implementation file appears unreferenced test/e2e/auth/per_node_update.go:1
  • medium Parallel implementation file sits beside a canonical file staging/src/k8s.io/apiserver/pkg/registry/rest/cr…:1
  • medium [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-a… hack/verify-flags-underscore.py:42
  • medium [COMP001] High cognitive complexity: Function `get_all_files` has cognitive com… hack/verify-flags-underscore.py:47
  • medium [COMP001] High cognitive complexity: Function `file_passes` has cognitive compl… hack/boilerplate/boilerplate.py:65
  • medium [COMP001] High cognitive complexity: Function `get_files` has cognitive complex… hack/boilerplate/boilerplate.py:158
  • medium [SEC094] Go: world-writable file permissions: File or directory created with wo… cmd/prune-junit-xml/prunexml.go:64
View all fragile runtime findings →
Config drift 15 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
12 matching findings on this repo
  • medium No CI/CD configuration found
  • high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… pkg/probe/http/http.go:41
  • medium Dockerfile runs as root: staging/src/k8s.io/client-go/examples/in-cluster-clien…
  • critical Possible secret in staging/src/k8s.io/cli-runtime/pkg/genericclioptions/config_… staging/src/k8s.io/cli-runtime/pkg/genericcliopti…:58
  • critical Possible secret in staging/src/k8s.io/client-go/rest/config.go staging/src/k8s.io/client-go/rest/config.go:205
  • low Very large file: staging/src/k8s.io/apiserver/pkg/server/config.go (1226 lines)
  • low Very large file: staging/src/k8s.io/apiserver/pkg/server/options/encryptionconf…
  • low Very large file: staging/src/k8s.io/client-go/applyconfigurations/utils.go (197…
  • low Very large file: staging/src/k8s.io/client-go/applyconfigurations/internal/inte…
  • low Very large file: staging/src/k8s.io/kubelet/config/v1beta1/types.go (1255 lines)
  • low Very large file: cluster/gce/gci/configure-helper.sh (3701 lines)
  • low Very large file: pkg/kubelet/apis/config/types.go (972 lines)
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/ff9a7d79-b095-4271-96e0-6710ec3d6b0f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ff9a7d79-b095-4271-96e0-6710ec3d6b0f/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.