kubernetes/kubernetes

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.

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

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

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 12 hours, 23 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

100.0% cov · 448 gaps

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

Severity: Critical 7 High 119 Medium 90 Low 383 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 178 9-layer 448 Crowd 0 Layer: Quality 432 Cicd 60 Software 48 Security 17 Network 18 Hardware 50 Frontend 1

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in cmd/kubeadm/app/util/users/users_linux.go

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in cmd/kubeadm/app/util/users/users_linux.go:83; move to env var / secrets manager.

cmd/kubeadm/app/util/users/users_linux.go:83

Possible secret in staging/src/k8s.io/cli-runtime/pkg/genericclioptions/config_flags.go

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in staging/src/k8s.io/cli-runtime/pkg/genericclioptions/config_flags.go:58; move to env var / secrets manager.

staging/src/k8s.io/cli-runtime/pkg/genericclioptions/config_flags.go:58

Possible secret in staging/src/k8s.io/client-go/rest/config.go

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in staging/src/k8s.io/client-go/rest/config.go:205; move to env var / secrets manager.

staging/src/k8s.io/client-go/rest/config.go:205

Possible secret in staging/src/k8s.io/client-go/tools/clientcmd/overrides.go

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in staging/src/k8s.io/client-go/tools/clientcmd/overrides.go:163; move to env var / secrets manager.

staging/src/k8s.io/client-go/tools/clientcmd/overrides.go:163

Insecure pattern 'eval_used' in staging/src/k8s.io/apiserver/pkg/authentication/cel/mapper.go:62

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

staging/src/k8s.io/apiserver/pkg/authentication/cel/mapper.go:62

Insecure pattern 'eval_used' in staging/src/k8s.io/client-go/tools/cache/synctrack/lazy.go:52

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

staging/src/k8s.io/client-go/tools/cache/synctrack/lazy.go:52

Insecure pattern 'exec_used' in staging/src/k8s.io/kubectl/pkg/cmd/exec/exec.go:90

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

staging/src/k8s.io/kubectl/pkg/cmd/exec/exec.go:90

Privileged port 254 in use

GapSeverity.MEDIUM Layer.NETWORK score 0.338

Why: medium severity · misconfigured network surface

Fix: If the number in cluster/addons/calico-policy-controller/felixconfigurations-crd.yaml is a real port, change the binding to ≥1024 or run behind a proxy.

cluster/addons/calico-policy-controller/felixconfigurations-crd.yaml

Privileged port 252 in use

GapSeverity.MEDIUM Layer.NETWORK score 0.338

Why: medium severity · misconfigured network surface

Fix: If the number in cluster/gce/gci/configure-helper.sh is a real port, change the binding to ≥1024 or run behind a proxy.

cluster/gce/gci/configure-helper.sh

#10

Privileged port 988 in use

GapSeverity.MEDIUM Layer.NETWORK score 0.338

Why: medium severity · misconfigured network surface

Fix: If the number in cluster/gce/gci/configure-helper.sh is a real port, change the binding to ≥1024 or run behind a proxy.

cluster/gce/gci/configure-helper.sh

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.