SREGym/SREGym

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.

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

Scan timing: clone 2.4s · analysis 19.37s · 4.5 MB · GitHub API rate-limit (preflight)

https://github.com/SREGym/SREGym · scanned 2026-06-05 23:42 UTC (4 days, 5 hours ago) · 10 languages

696 raw signals (344 security + 352 graph) 38th percentile · Python · medium (20-100K LoC) System graph score 71 (lower by 23)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 5 hours ago · v2 · 337 actionable findings from 2 signal sources. 178 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 · 144 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	8.0	0.25	2.00
`testing_score`	49.0	0.20	9.80
`documentation_score`	92.0	0.15	13.80
`practices_score`	76.0	0.15	11.40
`code_quality`	25.7	0.10	2.57
Overall		1.00	48.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 107 Medium 74 Low 95 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 193 System graph 144 Crowd 0 Layer: Quality 123 Security 34 Software 159 Cicd 11 Hardware 7 Frontend 1 Api 2

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

5 matching findings on this repo

low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 10 places
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

Commented-out code 21 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/`.

12 matching findings on this repo

info Commented-code block (9 lines) in tests/kubectl_tool_tests/nl2kubectl_agent.py:…
info Commented-code block (8 lines) in tests/results_preliminary/database.py:39
info Commented-code block (5 lines) in sregym/observer/tidb_prometheus.py:26
info Commented-code block (8 lines) in sregym/conductor/conductor.py:541
info Commented-code block (5 lines) in sregym/conductor/oracles/cronjob_sidecar_miti…
info Commented-code block (5 lines) in sregym/conductor/problems/khaos_faults.py:152
info Commented-code block (7 lines) in sregym/conductor/problems/expired_tls_hotel_r…
info Commented-code block (6 lines) in sregym/conductor/problems/capacity_decrease_r…
info Commented-code block (5 lines) in sregym/conductor/problems/admission_webhook_o…
info Commented-code block (6 lines) in sregym/conductor/problems/cronjob_sidecar_blo…
info Commented-code block (5 lines) in sregym/service/kubectl.py:211
info Commented-code block (7 lines) in sregym/service/container_runner.py:153

View all commented-out code findings →

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

2 matching findings on this repo

high Phantom test coverage: test_smoke_misconfig_app_hotel_res tests/integration/smoke_test.py:57
low Possibly dead Python function: configmap_uid sregym/conductor/oracles/diagnosis_oracle.py:272

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/337beb47-d253-40ad-92fe-c1cc6096b5c8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/337beb47-d253-40ad-92fe-c1cc6096b5c8/

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.