kubernetes-sigs/inference-perf

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.

77 of your 136 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.99s · analysis 5.09s · 10.6 MB · GitHub API rate-limit (preflight)

https://github.com/kubernetes-sigs/inference-perf · scanned 2026-06-05 19:52 UTC (4 days, 15 hours ago) · 10 languages

234 raw signals (130 security + 104 graph) 56th percentile · Python · medium (20-100K LoC) System graph score 82 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 15 hours ago · v2 · 99 actionable findings from 2 signal sources. 58 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 35 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	32.1	0.25	8.03
`testing_score`	100.0	0.20	20.00
`documentation_score`	88.0	0.15	13.20
`practices_score`	84.0	0.15	12.60
`code_quality`	47.3	0.10	4.73
Overall		1.00	67.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 12 Medium 9 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 64 System graph 35 Crowd 0 Layer: Software 17 Cicd 8 Security 7 Quality 63 Api 1 Hardware 2 Frontend 1

Exclude dismissed / FP Exclude test files

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.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Commented-out code 7 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

7 matching findings on this repo

info Commented-code block (5 lines) in tests/test_otel_trace_to_replay_graph.py:446
info Commented-code block (7 lines) in inference_perf/client/modelserver/openai_clie…
info Commented-code block (5 lines) in inference_perf/datagen/replay_graph_session_d…
info Commented-code block (5 lines) in inference_perf/datagen/shared_prefix_datagen.…
info Commented-code block (5 lines) in inference_perf/loadgen/load_generator.py:692
info Commented-code block (7 lines) in inference_perf/apis/chat.py:99
info Commented-code block (5 lines) in e2e/tests/test_llm_d_inference_sim.py:211

View all commented-out code findings →

Config drift 5 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.

5 matching findings on this repo

high Phantom test coverage: test_simple_storage_service_config_rejects_invalid_addre… tests/test_config.py:364
high Phantom test coverage: test_prometheus_client_config_validation tests/test_config.py:215
high Phantom test coverage: test_load_config_validation tests/test_config.py:179
high Phantom test coverage: test_requires_conversation_replay_config tests/test_conversation_replay_datagen.py:157
high Insecure pattern 'eval_used' in inference_perf/config/datagen/replay.py:128 inference_perf/config/datagen/replay.py:128

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/def834f7-1e77-4438-ad9f-7f593101ea91/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/def834f7-1e77-4438-ad9f-7f593101ea91/

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.