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.
Sign up free Scan another repo

wrodrigobr/Leaklab

https://github.com/wrodrigobr/Leaklab · scanned 2026-06-16 01:01 UTC (2 months, 1 week ago)

257 raw signals (0 security + 257 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 232 actionable findings from 1 signal source. 25 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
46.2
/100
Security checks
46
0 findings
System graph
46
100.0% cov · 232 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 35 Medium 38 Low 99 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 232 Crowd 0 Layer: Software 13 Frontend 37 Security 30 Network 1 Hardware 3 Cicd 1 Quality 63 Api 84
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 46.2/100 with 100.0% coverage. It contains 4495 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 257 findings — concentrated in quality (85), api (84), frontend (37). Risk profile is high: 0 critical, 35 high, 43 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 172 of 232 actionable findings. 257 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /admin/users/${id} (frontend/src/lib/api.ts:2008)
`frontend/src/lib/api.ts:2008` calls `DELETE /admin/users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /coach/student/${studentId}/baseline (frontend/src/lib/api.ts:1709)
`frontend/src/lib/api.ts:1709` calls `DELETE /coach/student/${studentId}/baseline` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/baseline` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /coach/student/${studentId}/hand-annotations/${decisionId} (frontend/src/lib/api.ts:1679)
`frontend/src/lib/api.ts:1679` calls `DELETE /coach/student/${studentId}/hand-annotations/${decisionId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/hand-annotations/<p>` If this points…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /coach/student/${studentId}/study-overrides/${encodeURIComponent(cardSpot)} (frontend/src/lib/api.ts:1659)
`frontend/src/lib/api.ts:1659` calls `DELETE /coach/student/${studentId}/study-overrides/${encodeURIComponent(cardSpot)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/study-overrides/<p>…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /coach/templates/${templateId} (frontend/src/lib/api.ts:1748)
`frontend/src/lib/api.ts:1748` calls `DELETE /coach/templates/${templateId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/templates/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /history/tournament/${tournamentId} (frontend/src/lib/api.ts:464)
`frontend/src/lib/api.ts:464` calls `DELETE /history/tournament/${tournamentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/history/tournament/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/${coachId}/contact-thread (frontend/src/lib/api.ts:2178)
`frontend/src/lib/api.ts:2178` calls `GET /coach/${coachId}/contact-thread` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/<p>/contact-thread` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/activity-feed?limit=${limit} (frontend/src/lib/api.ts:1714)
`frontend/src/lib/api.ts:1714` calls `GET /coach/student/${studentId}/activity-feed?limit=${limit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/activity-feed` If this points at an exter…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/breakdown?days=${days} (frontend/src/lib/api.ts:1626)
`frontend/src/lib/api.ts:1626` calls `GET /coach/student/${studentId}/breakdown?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/breakdown` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/hand-annotations (frontend/src/lib/api.ts:1664)
`frontend/src/lib/api.ts:1664` calls `GET /coach/student/${studentId}/hand-annotations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/hand-annotations` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/history?days=${days} (frontend/src/lib/api.ts:1620)
`frontend/src/lib/api.ts:1620` calls `GET /coach/student/${studentId}/history?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/history` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/level (frontend/src/lib/api.ts:1617)
`frontend/src/lib/api.ts:1617` calls `GET /coach/student/${studentId}/level` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/level` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/messages (frontend/src/lib/api.ts:1752)
`frontend/src/lib/api.ts:1752` calls `GET /coach/student/${studentId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/messages` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/progress-report (frontend/src/lib/api.ts:1717)
`frontend/src/lib/api.ts:1717` calls `GET /coach/student/${studentId}/progress-report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/progress-report` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/replay/${tournamentId}/${handId} (frontend/src/lib/api.ts:1642)
`frontend/src/lib/api.ts:1642` calls `GET /coach/student/${studentId}/replay/${tournamentId}/${handId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/replay/<p>/<p>` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/stats?days=${days} (frontend/src/lib/api.ts:1623)
`frontend/src/lib/api.ts:1623` calls `GET /coach/student/${studentId}/stats?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/stats` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coach/student/${studentId}/study-overrides (frontend/src/lib/api.ts:1645)
`frontend/src/lib/api.ts:1645` calls `GET /coach/student/${studentId}/study-overrides` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/study-overrides` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /coaches/${coachUserId} (frontend/src/lib/api.ts:1823)
`frontend/src/lib/api.ts:1823` calls `GET /coaches/${coachUserId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coaches/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /player/session-review/${tournamentId} (frontend/src/lib/api.ts:1142)
`frontend/src/lib/api.ts:1142` calls `GET /player/session-review/${tournamentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/player/session-review/<p>` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /player/spots/drill/${decision_id}/analysis (frontend/src/lib/api.ts:830)
`frontend/src/lib/api.ts:830` calls `GET /player/spots/drill/${decision_id}/analysis` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/player/spots/drill/<p>/analysis` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /replay/${decisionId}/gto (frontend/src/lib/api.ts:2278)
`frontend/src/lib/api.ts:2278` calls `GET /replay/${decisionId}/gto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/replay/<p>/gto` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /replay/${tournamentId}/${handId} (frontend/src/lib/api.ts:444)
`frontend/src/lib/api.ts:444` calls `GET /replay/${tournamentId}/${handId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/replay/<p>/<p>` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/finance/coaches/${paymentId}/pay (frontend/src/lib/api.ts:2019)
`frontend/src/lib/api.ts:2019` calls `PATCH /admin/finance/coaches/${paymentId}/pay` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/finance/coaches/<p>/pay` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/users/${id} (frontend/src/lib/api.ts:2002)
`frontend/src/lib/api.ts:2002` calls `PATCH /admin/users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/coach-applications/${id}/approve (frontend/src/lib/api.ts:2027)
`frontend/src/lib/api.ts:2027` calls `POST /admin/coach-applications/${id}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/coach-applications/<p>/approve` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/coach-applications/${id}/reject (frontend/src/lib/api.ts:2033)
`frontend/src/lib/api.ts:2033` calls `POST /admin/coach-applications/${id}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/coach-applications/<p>/reject` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/support-tickets/${ticketId}/reply (frontend/src/lib/api.ts:2304)
`frontend/src/lib/api.ts:2304` calls `POST /admin/support-tickets/${ticketId}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/support-tickets/<p>/reply` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /coach/${coachId}/contact (frontend/src/lib/api.ts:2172)
`frontend/src/lib/api.ts:2172` calls `POST /coach/${coachId}/contact` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/<p>/contact` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /coach/student/${studentId}/baseline (frontend/src/lib/api.ts:1703)
`frontend/src/lib/api.ts:1703` calls `POST /coach/student/${studentId}/baseline` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/baseline` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /coach/student/${studentId}/hand-annotations (frontend/src/lib/api.ts:1673)
`frontend/src/lib/api.ts:1673` calls `POST /coach/student/${studentId}/hand-annotations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/hand-annotations` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /coach/student/${studentId}/messages (frontend/src/lib/api.ts:1755)
`frontend/src/lib/api.ts:1755` calls `POST /coach/student/${studentId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/messages` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /coach/student/${studentId}/study-overrides (frontend/src/lib/api.ts:1653)
`frontend/src/lib/api.ts:1653` calls `POST /coach/student/${studentId}/study-overrides` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/coach/student/<p>/study-overrides` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /player/hands/${handId}/request-gto (frontend/src/lib/api.ts:447)
`frontend/src/lib/api.ts:447` calls `POST /player/hands/${handId}/request-gto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/player/hands/<p>/request-gto` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /player/notifications/${id}/read (frontend/src/lib/api.ts:1013)
`frontend/src/lib/api.ts:1013` calls `POST /player/notifications/${id}/read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/player/notifications/<p>/read` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env
`frontend/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
frontend/.env ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/ui/chart.tsx:70
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/Docs.tsx:194
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/DocsRating.tsx:10
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/replayer/RangePanel.tsx:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph security Analyzer error conf 1.00 Analyzer timeout: security.gitleaks
analyzer exceeded 60.0s wall-clock (thread mode — daemon abandoned). Bump REPOBILITY_ANALYZER_TIMEOUT_S if expected.
Timeout
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 6 occurrences Frontend route `/tournaments/compare` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/api/app.py:209
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/api/app.py:209 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/ui/chart.tsx:70
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/ui/chart.tsx:70 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/pages/Docs.tsx:194
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/pages/Docs.tsx:194 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/index.legacy.html:899
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/index.legacy.html:899 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/leaklab-replayer-v3.html:710
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/leaklab-replayer-v3.html:710 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/leaklab-replayer-v4.html:692
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/leaklab-replayer-v4.html:692 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/components/hud/PokerTableV3.tsx:521
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/components/hud/PokerTableV3.tsx:521 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/index.legacy.html:2069
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/index.legacy.html:2069 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/faces_squeeze_card_shots.mjs:21
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/faces_squeeze_card_shots.mjs:21 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/limp_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/limp_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/mobile_shots.mjs:13
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/mobile_shots.mjs:13 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/multiway_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/multiway_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/pf_uncov_shots.mjs:15
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/pf_uncov_shots.mjs:15 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/postflop_card_shots.mjs:16
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/postflop_card_shots.mjs:16 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/pushfold_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/pushfold_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/rangepanel_shots.mjs:15
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/rangepanel_shots.mjs:15 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/replayer_shots.mjs:33
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/replayer_shots.mjs:33 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/rfi_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/rfi_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/river_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/river_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/squeeze_card_shots.mjs:16
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/squeeze_card_shots.mjs:16 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/turn_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/turn_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/vs3bet_card_shots.mjs:21
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/vs3bet_card_shots.mjs:21 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/vs4bet_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/vs4bet_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/vs_rfi_card_shots.mjs:16
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/vs_rfi_card_shots.mjs:16 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/vs_shove_card_shots.mjs:17
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/vs_shove_card_shots.mjs:17 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/scripts/vsrfi_fresh_shots.mjs:15
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/scripts/vsrfi_fresh_shots.mjs:15 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/lib/auth.tsx:34
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/lib/auth.tsx:34 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/scripts/gto_validation/playwright_compare.py:583
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 131 placeholder/mock markers across 38 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 42 in use
Port 42 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
backend/gto_bot/solver_api/setup_vm.sh Ports
low System graph quality Integrity conf 1.00 57 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOWED_ORIGINS`, `ANTHROPIC_API_KEY`, `APP_BASE_URL`, `CDP_PORT`, `COACH_CHAT_AGENTIC`, `DATABASE_URL`, `DEEP_DIVE_AGENTIC`, `DIGEST_FROM` + 49 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1754 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 17, 20, 37, 86
.github/workflows/ci-cd.yml:17, 20, 37, 86 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'debug_true' in backend/api/app.py:7436
Found a known-risky pattern (debug_true). Review and replace if possible.
backend/api/app.py:7436 Debug true
low System graph quality Tests conf 1.00 Low test-to-source ratio
75 tests / 425 src (ratio 0.18).
low System graph quality Integrity conf 1.00 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/api/app.py:history_tournaments, backend/api/app.py:history_tournament This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
13 occurrences
repo-level (13 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/scripts/sync_gto_labels_from_ranges.py:parse_cards, backend/scripts/sync_gto_labels_from_solver.py:parse_cards, backend/scripts/list_uncovered_vsrfi.py:parse_cards This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos —…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/scripts/gto_validation/playwright_compare.py:on_req, backend/scripts/gto_validation/playwright_compare.py:on_req, backend/scripts/gto_validation/_probe_gametypes.py:on_req, backend/scripts/gto_validation/smoke_test_multiway.py:on_req This is …
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `coach_students_v2` in backend/api/app.py:2061
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `digest_unsub_v1` in backend/leaklab/email_digest.py:31
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `is_legacy` in backend/database/repositories.py:106
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `parse_spot_v2` in backend/scripts/parse_gw_har.py:46
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `purged_solver_cli_nodes_backup` in backend/scripts/postflop_correctness_audit.py:115
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `study_plan_agentic_v1` in backend/leaklab/llm_explainer.py:1401
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_study_plan_cache_key_v2` in backend/tests/test_study_plan.py:114
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: build_app_url
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/gto_validation/playwright_compare.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: build_preflop_actions_simple
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/gto_validation/preflop_action_builder.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/gto_bot/solver_api/server.py:1258
low System graph software Dead code conf 1.00 Possibly dead Python function: do_login
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/gto_validation/playwright_compare.py:159
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/gto_bot/solver_api/server.py:1279
low System graph software Dead code conf 1.00 Possibly dead Python function: is_divergent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/leaklab/coach_adherence.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: load_cookies
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/gto_validation/playwright_compare.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/gto_bot/solver_api/server.py:1232
low System graph software Dead code conf 1.00 Possibly dead Python function: matcher
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/gto_bot/solver_api/_gw_subprocess.py:93
low System graph software Dead code conf 1.00 Possibly dead Python function: ph
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/database/schema.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: placeholders
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/database/schema.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: position_from_preflop_actions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/parse_gw_har.py:223
low System graph software Dead code conf 1.00 Possibly dead Python function: resync_gto_labels_for_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/database/repositories.py:6718
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/gto_validation/console_script.js:523
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/pages/Replayer.tsx:1650
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — backend/gto_bot/solver_api/server.py:1232
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analyze
`backend/api/app.py` declares `ANY /analyze` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analyze/guest
`backend/api/app.py` declares `ANY /analyze/guest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analyze/hand-coach
`backend/api/app.py` declares `ANY /analyze/hand-coach` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analyze/replay-coach
`backend/api/app.py` declares `ANY /analyze/replay-coach` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/<int:coach_id>/contact
`backend/api/app.py` declares `ANY /coach/<int:coach_id>/contact` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/<int:coach_id>/contact-thread
`backend/api/app.py` declares `ANY /coach/<int:coach_id>/contact-thread` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/my-review
`backend/api/app.py` declares `ANY /coach/my-review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/activity-feed
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/activity-feed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/baseline
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/baseline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/breakdown
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/breakdown` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/hand-annotations
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/hand-annotations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/hand-annotations/<int:decision_id>
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/hand-annotations/<int:decision_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/history
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/level
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/level` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/messages
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/progress-report
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/progress-report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/replay/<tournament_id>/<hand_id>
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/replay/<tournament_id>/<hand_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/stats
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/study-overrides
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/study-overrides` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/study-overrides/<path:card_spot>
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/study-overrides/<path:card_spot>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/study-plan
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/study-plan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/tournament/<tournament_id>
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/tournament/<tournament_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/student/<int:student_id>/worst-decisions
`backend/api/app.py` declares `ANY /coach/student/<int:student_id>/worst-decisions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/students-legacy
`backend/api/app.py` declares `ANY /coach/students-legacy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coach/templates/<int:template_id>
`backend/api/app.py` declares `ANY /coach/templates/<int:template_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coaches
`backend/api/app.py` declares `ANY /coaches` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coaches/<int:coach_user_id>
`backend/api/app.py` declares `ANY /coaches/<int:coach_user_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /coaches/<int:coach_user_id>/reviews
`backend/api/app.py` declares `ANY /coaches/<int:coach_user_id>/reviews` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /gto/status
`backend/api/app.py` declares `ANY /gto/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/evolution
`backend/api/app.py` declares `ANY /history/evolution` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournament/<tournament_id>
`backend/api/app.py` declares `ANY /history/tournament/<tournament_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournament/<tournament_id>/narrative
`backend/api/app.py` declares `ANY /history/tournament/<tournament_id>/narrative` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournament/<tournament_id>/phase_analysis
`backend/api/app.py` declares `ANY /history/tournament/<tournament_id>/phase_analysis` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournament/<tournament_id>/report.pdf
`backend/api/app.py` declares `ANY /history/tournament/<tournament_id>/report.pdf` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournament/<tournament_id>/texture_analysis
`backend/api/app.py` declares `ANY /history/tournament/<tournament_id>/texture_analysis` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /history/tournaments/compare
`backend/api/app.py` declares `ANY /history/tournaments/compare` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/ev-leaks
`backend/api/app.py` declares `ANY /player/ev-leaks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/gto-alignment
`backend/api/app.py` declares `ANY /player/gto-alignment` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/gto-alignment-matrix
`backend/api/app.py` declares `ANY /player/gto-alignment-matrix` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/gto-position
`backend/api/app.py` declares `ANY /player/gto-position` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/gto-quality
`backend/api/app.py` declares `ANY /player/gto-quality` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/leak-finder
`backend/api/app.py` declares `ANY /player/leak-finder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/leak-roi
`backend/api/app.py` declares `ANY /player/leak-roi` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/notifications/<int:notif_id>/read
`backend/api/app.py` declares `ANY /player/notifications/<int:notif_id>/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/results-vs-gto
`backend/api/app.py` declares `ANY /player/results-vs-gto` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/session-review/<int:tournament_id>
`backend/api/app.py` declares `ANY /player/session-review/<int:tournament_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/sparring/hand
`backend/api/app.py` declares `ANY /player/sparring/hand` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/spots/drill
`backend/api/app.py` declares `ANY /player/spots/drill` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /player/spots/drill/<int:decision_id>/analysis
`backend/api/app.py` declares `ANY /player/spots/drill/<int:decision_id>/analysis` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /study/plan
`backend/api/app.py` declares `ANY /study/plan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/api/app.py (7436 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/database/repositories.py (6948 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/database/schema.py (1637 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/gto_bot/solver_api/server.py (1358 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/leaklab/academy.py (1307 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/leaklab/decision_engine_v11.py (1181 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/leaklab/llm_explainer.py (2886 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/leaklab/preflop_gto_ranges.py (1327 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/api.ts (2308 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/admin/AdminDashboard.tsx (1241 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/coach/CoachDashboard.tsx (1364 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/coach/StudentDetail.tsx (1695 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/GhostTable.tsx (1131 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/HandBuilder.tsx (1246 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/Replayer.tsx (2024 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/babd7f35-f449-4c33-bcff-58bce0d99f30/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/babd7f35-f449-4c33-bcff-58bce0d99f30/

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.