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

thomasbeaumonttb24-del/blackturf

https://github.com/thomasbeaumonttb24-del/blackturf · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

169 raw signals (0 security + 169 graph)

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

Complete repo analysis

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

JSON
Combined
50.5
/100
Security checks
51
0 findings
System graph
51
100.0% cov · 142 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 8 Medium 10 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 142 Crowd 0 Layer: Software 16 Frontend 16 Hardware 4 Security 9 Cicd 3 Quality 44 Api 50
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 50.5/100 with 100.0% coverage. It contains 2200 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 169 findings — concentrated in quality (60), api (50), software (16). Risk profile is high: 0 critical, 8 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 110 of 142 actionable findings. 169 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 quality Integrity conf 1.00 Blocking `urllib.request.urlopen(...)` inside `async def validate` — backend/scripts/validate_pmu_integrity.py:43
Sync I/O inside an async function blocks the event loop. While `urllib.request.urlopen(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asy…
backend/scripts/validate_pmu_integrity.py:43 Sync io in asyncPerformance
high System graph security auth conf 1.00 FastAPI POST `forgot_password` without auth dependency — backend/api/routes/auth.py:379
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/auth.py:379 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `google_oauth` without auth dependency — backend/api/routes/auth.py:221
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/auth.py:221 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_betfair` without auth dependency — backend/api/routes/admin.py:1290
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/admin.py:1290 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh` without auth dependency — backend/api/routes/auth.py:204
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/auth.py:204 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_password` without auth dependency — backend/api/routes/auth.py:421
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/auth.py:421 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — backend/api/routes/stripe_routes.py:116
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/stripe_routes.py:116 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_webhook` without auth dependency — backend/api/routes/telegram.py:18
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/routes/telegram.py:18 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/layout/Navbar.tsx:48
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 quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/.claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
frontend/.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/login-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 32, 39, 44, 52, 64, 72, 95
.github/workflows/deploy.yml:32, 39, 44, 52, 64, 72, 95 (7 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/lib/api.ts:41
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/lib/api.ts:41 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/lib/auth.ts:27
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/lib/auth.ts:27 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 37 placeholder/mock markers across 18 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 12 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BETFAIR_APPKEY`, `BETFAIR_COUNTRIES`, `BETFAIR_PASS`, `BETFAIR_USER`, `BLACKTURF_ALLOW_SEED`, `BLACKTURF_INGEST_TOKEN`, `BLACKTURF_INGEST_URL`, `NEXT_PUBLIC_API_URL` + 4 more. Add them (with a placeholder/comment) to .env.example so onboarding doe…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 180 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 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 5, 17
frontend/Dockerfile:1, 5, 17 (3 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-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/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 22, 50, 79, 104
.github/workflows/ci.yml:22, 50, 79, 104 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
33 tests / 179 src (ratio 0.18).
low System graph quality Integrity conf 1.00 17 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/api/routes/bankroll.py:export_bankroll_csv, backend/api/routes/bankroll.py:export_bankroll_pdf 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…
17 occurrences
repo-level (17 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/api/routes/admin.py:change_user_plan, backend/api/routes/admin.py:update_user, backend/api/routes/admin.py:adjust_bankroll This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `export_csv_legacy` in backend/api/routes/bankroll.py:355
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 `mean_old` in backend/ml/drift_detector.py:185
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 `p_copy` in backend/ml/portfolio.py:596
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 `triangulation_cotes_v2` in backend/ml/valuebets.py:112
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 `triangulation_cotes_v2` in backend/tests/test_ml_units.py:7
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: compute_features_for_participation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/features.py:272
low System graph software Dead code conf 1.00 Possibly dead Python function: cout_combo
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/recommendations.py:75
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scraper/base.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: latest_edge_monitor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/edge_monitor.py:109
low System graph software Dead code conf 1.00 Possibly dead Python function: optimize_multi_race_portfolio
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/portfolio.py:890
low System graph software Dead code conf 1.00 Possibly dead Python function: p_tierce_ordre
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/combo_bets.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: push_alert_to_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/routes/ws.py:393
low System graph software Dead code conf 1.00 Possibly dead Python function: rate_limit_assistant
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/middleware/rate_limit.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: rate_limit_predictions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/middleware/rate_limit.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: rate_limit_public
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/middleware/rate_limit.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/routes/auth.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: require_pro
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/api/routes/auth.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: retry_async
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scraper/base.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: save_temps_passage
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scraper/db_writer.py:703
low System graph software Dead code conf 1.00 Possibly dead Python function: should_retrain
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/ml/post_race_analyzer.py:614
low System graph software Dead code conf 1.00 Possibly dead Python function: work
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/audit_schema_drift.py:19
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 — frontend/src/app/layout.tsx:95
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 api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/bankroll/entries/{entry_id}
`backend/api/routes/bankroll.py` declares `DELETE /api/v1/bankroll/entries/{entry_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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/bankroll/portefeuilles/{bankroll_id}
`backend/api/routes/bankroll.py` declares `DELETE /api/v1/bankroll/portefeuilles/{bankroll_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: DELETE /api/v1/notifications/all
`backend/api/routes/notifications.py` declares `DELETE /api/v1/notifications/all` 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: GET /admin/api/dashboard
`backend/api/routes/admin.py` declares `GET /admin/api/dashboard` 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: GET /admin/api/users
`backend/api/routes/admin.py` declares `GET /admin/api/users` 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: GET /admin/api/users/{user_id}
`backend/api/routes/admin.py` declares `GET /admin/api/users/{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: GET /api/v1/assistant/suggestions
`backend/api/routes/assistant.py` declares `GET /api/v1/assistant/suggestions` 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: GET /api/v1/auth/me
`backend/api/routes/auth.py` declares `GET /api/v1/auth/me` 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: GET /api/v1/auth/verify-email
`backend/api/routes/auth.py` declares `GET /api/v1/auth/verify-email` 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: GET /api/v1/bankroll/entries
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/entries` 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: GET /api/v1/bankroll/export
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/export` 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: GET /api/v1/bankroll/export/csv
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/export/csv` 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: GET /api/v1/bankroll/export/pdf
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/export/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/bankroll/portefeuilles
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/portefeuilles` 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: GET /api/v1/bankroll/stats
`backend/api/routes/bankroll.py` declares `GET /api/v1/bankroll/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: GET /api/v1/courses/{course_id}/analyse
`backend/api/routes/predictions.py` declares `GET /api/v1/courses/{course_id}/analyse` 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: GET /api/v1/courses/{course_id}/dutch
`backend/api/routes/predictions.py` declares `GET /api/v1/courses/{course_id}/dutch` 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: GET /api/v1/courses/{course_id}/feature-importance
`backend/api/routes/predictions.py` declares `GET /api/v1/courses/{course_id}/feature-importance` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/courses/{course_id}/predictions
`backend/api/routes/predictions.py` declares `GET /api/v1/courses/{course_id}/predictions` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/health
`backend/api/main.py` declares `GET /api/v1/health` 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: GET /api/v1/model/version
`backend/api/routes/predictions.py` declares `GET /api/v1/model/version` 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: GET /api/v1/notifications/
`backend/api/routes/notifications.py` declares `GET /api/v1/notifications/` 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: GET /api/v1/notifications/count-unread
`backend/api/routes/notifications.py` declares `GET /api/v1/notifications/count-unread` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/notifications/prefs
`backend/api/routes/notifications.py` declares `GET /api/v1/notifications/prefs` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/pari-du-jour
`backend/api/routes/predictions.py` declares `GET /api/v1/pari-du-jour` 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: GET /api/v1/pari-du-jour-profils
`backend/api/routes/predictions.py` declares `GET /api/v1/pari-du-jour-profils` 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: GET /api/v1/value-bets
`backend/api/routes/predictions.py` declares `GET /api/v1/value-bets` 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: GET /api/v1/value-bets/historique
`backend/api/routes/predictions.py` declares `GET /api/v1/value-bets/historique` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/auth/me
`backend/api/routes/auth.py` declares `PATCH /api/v1/auth/me` 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: PATCH /api/v1/bankroll/entries/{entry_id}
`backend/api/routes/bankroll.py` declares `PATCH /api/v1/bankroll/entries/{entry_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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/assistant/chat
`backend/api/routes/assistant.py` declares `POST /api/v1/assistant/chat` 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: POST /api/v1/auth/forgot-password
`backend/api/routes/auth.py` declares `POST /api/v1/auth/forgot-password` 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: POST /api/v1/auth/google
`backend/api/routes/auth.py` declares `POST /api/v1/auth/google` 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: POST /api/v1/auth/login
`backend/api/routes/auth.py` declares `POST /api/v1/auth/login` 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: POST /api/v1/auth/refresh
`backend/api/routes/auth.py` declares `POST /api/v1/auth/refresh` 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: POST /api/v1/auth/register
`backend/api/routes/auth.py` declares `POST /api/v1/auth/register` 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: POST /api/v1/auth/resend-verification
`backend/api/routes/auth.py` declares `POST /api/v1/auth/resend-verification` 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: POST /api/v1/auth/reset-password
`backend/api/routes/auth.py` declares `POST /api/v1/auth/reset-password` 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: POST /api/v1/bankroll/entries
`backend/api/routes/bankroll.py` declares `POST /api/v1/bankroll/entries` 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: POST /api/v1/bankroll/portefeuilles
`backend/api/routes/bankroll.py` declares `POST /api/v1/bankroll/portefeuilles` 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: POST /api/v1/courses/{course_id}/predict
`backend/api/routes/predictions.py` declares `POST /api/v1/courses/{course_id}/predict` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/stripe/checkout
`backend/api/routes/stripe_routes.py` declares `POST /api/v1/stripe/checkout` 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: POST /api/v1/stripe/portal
`backend/api/routes/stripe_routes.py` declares `POST /api/v1/stripe/portal` 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: POST /api/v1/stripe/webhook
`backend/api/routes/stripe_routes.py` declares `POST /api/v1/stripe/webhook` 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: POST /api/v1/telegram/setup-webhook
`backend/api/routes/telegram.py` declares `POST /api/v1/telegram/setup-webhook` 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: POST /api/v1/telegram/webhook
`backend/api/routes/telegram.py` declares `POST /api/v1/telegram/webhook` 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: PUT /api/v1/auth/push-subscription
`backend/api/routes/auth.py` declares `PUT /api/v1/auth/push-subscription` 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: PUT /api/v1/bankroll/portefeuilles/{bankroll_id}
`backend/api/routes/bankroll.py` declares `PUT /api/v1/bankroll/portefeuilles/{bankroll_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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/notifications/prefs
`backend/api/routes/notifications.py` declares `PUT /api/v1/notifications/prefs` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/notifications/{alerte_id}/lue
`backend/api/routes/notifications.py` declares `PUT /api/v1/notifications/{alerte_id}/lue` 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 …
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/api/routes/admin.py (1374 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/api/routes/courses.py (2238 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/db/models.py (1011 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/ml/features.py (2329 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/ml/pipeline.py (1748 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mise_calculator.py (1087 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/app/(main)/courses/[id]/page.tsx (2759 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/3db7efec-bac5-4bf0-be0f-e47f6c863578/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3db7efec-bac5-4bf0-be0f-e47f6c863578/

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.