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.

alpha112233/alphago_live

https://github.com/alpha112233/alphago_live · scanned 2026-06-17 01:33 UTC (1 month, 2 weeks ago)

447 raw signals (0 security + 447 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -27.6 (diff) · 404 actionable findings from 1 signal source. 43 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 · 404 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 36 High 90 Medium 37 Low 124 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 404 Crowd 0 Layer: Software 14 Frontend 28 Network 2 Hardware 3 Security 43 Cicd 4 Quality 171 Api 139

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

12 matching findings on this repo

low Near-duplicate function bodies in 9 places repo-level
low Near-duplicate function bodies in 10 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 18 places
low Near-duplicate function bodies in 12 places
low Near-duplicate function bodies in 28 places repo-level
low Near-duplicate function bodies in 11 places
low Near-duplicate function bodies in 24 places
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 6 places repo-level
low Near-duplicate function bodies in 7 places repo-level
low Near-duplicate function bodies in 17 places

View all duplicates & near-duplicates findings →

Commented-out code 91 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 (6 lines) in app.py:317
info Commented-code block (7 lines) in broker/wisdom/streaming/wisdom_websocket.py:2…
info Commented-code block (7 lines) in broker/wisdom/database/master_contract_db.py:…
info Commented-code block (9 lines) in broker/deltaexchange/api/data.py:367
info Commented-code block (5 lines) in broker/deltaexchange/mapping/order_data.py:63
info Commented-code block (6 lines) in broker/deltaexchange/streaming/delta_adapter.…
info Commented-code block (8 lines) in broker/deltaexchange/streaming/delta_websocke…
info Commented-code block (6 lines) in broker/deltaexchange/database/master_contract…
info Commented-code block (7 lines) in broker/nubra/api/nubrawebsocket.py:405
info Commented-code block (5 lines) in broker/zerodha/api/data.py:17
info Commented-code block (8 lines) in broker/zerodha/mapping/margin_data.py:172
info Commented-code block (5 lines) in broker/zerodha/streaming/zerodha_mapping.py:18

View all commented-out code findings →

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

6 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
high Dangling fetch: GET /auth/broker-config (frontend/src/pages/BrokerSelect.tsx:96)
high Dangling fetch: GET /auth/broker-config (frontend/src/pages/BrokerSelect.tsx:14…
high Dangling fetch: GET /sandbox/api/configs (frontend/src/pages/Sandbox.tsx:94)
high Dangling fetch: GET /auth/sso-config (frontend/src/pages/Login.tsx:33)
low Unused endpoint: ANY /<int:strategy_id>/configure

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/df7a8a42-7edf-49dc-84de-ec89dd61428d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/df7a8a42-7edf-49dc-84de-ec89dd61428d/

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.