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

Rifferd/diffduel

https://github.com/Rifferd/diffduel · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

179 raw signals (0 security + 179 graph)

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

Complete repo analysis

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

JSON
Combined
45.7
/100
Security checks
46
0 findings
System graph
46
100.0% cov · 149 findings
Critical
1
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 1 High 59 Medium 9 Low 74 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 149 Crowd 0 Layer: Software 9 Frontend 1 Hardware 7 Security 20 Cicd 3 Quality 18 Api 91
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 45.7/100 with 100.0% coverage. It contains 2366 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 179 findings — concentrated in api (91), quality (26), security (20). Risk profile is high: 1 critical, 59 high, 16 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 143 of 149 actionable findings. 179 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.

critical System graph security Secrets conf 1.00 Possible secret in infra/load/k6/lib/common.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
infra/load/k6/lib/common.js:69
high System graph api Wiring conf 1.00 Dangling fetch: GET /a (apps/web/src/shared/api/client.test.ts:118)
`apps/web/src/shared/api/client.test.ts:118` calls `GET /a` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/a` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/feature-flags (apps/admin/src/shared/api/endpoints.ts:148)
`apps/admin/src/shared/api/endpoints.ts:148` calls `GET /admin/feature-flags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/feature-flags` 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 /admin/metrics/overview (apps/admin/src/shared/api/endpoints.ts:59)
`apps/admin/src/shared/api/endpoints.ts:59` calls `GET /admin/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/metrics/overview` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /ai/review/${duelId} (apps/web/src/shared/api/endpoints.ts:230)
`apps/web/src/shared/api/endpoints.ts:230` calls `GET /ai/review/${duelId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/review/<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: GET /b (apps/web/src/shared/api/client.test.ts:119)
`apps/web/src/shared/api/client.test.ts:119` calls `GET /b` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/b` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /daily/leaderboard${qs} (apps/web/src/shared/api/endpoints.ts:217)
`apps/web/src/shared/api/endpoints.ts:217` calls `GET /daily/leaderboard${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/daily/leaderboard/<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: GET /me/duels${qs} (apps/web/src/shared/api/endpoints.ts:180)
`apps/web/src/shared/api/endpoints.ts:180` calls `GET /me/duels${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/duels/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /me/stats${qs} (apps/web/src/shared/api/endpoints.ts:188)
`apps/web/src/shared/api/endpoints.ts:188` calls `GET /me/stats${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/stats/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /tournaments${qs} (apps/admin/src/shared/api/endpoints.ts:127)
`apps/admin/src/shared/api/endpoints.ts:127` calls `GET /tournaments${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<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: GET /tournaments${qs} (apps/web/src/shared/api/endpoints.ts:291)
`apps/web/src/shared/api/endpoints.ts:291` calls `GET /tournaments${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /tournaments/${id} (apps/web/src/shared/api/endpoints.ts:295)
`apps/web/src/shared/api/endpoints.ts:295` calls `GET /tournaments/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<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: GET /tournaments/${id}/tasks (apps/web/src/shared/api/endpoints.ts:303)
`apps/web/src/shared/api/endpoints.ts:303` calls `GET /tournaments/${id}/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<p>/tasks` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/tasks/${id} (apps/admin/src/shared/api/endpoints.ts:84)
`apps/admin/src/shared/api/endpoints.ts:84` calls `PATCH /admin/tasks/${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/tasks/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /admin/tournaments/${id} (apps/admin/src/shared/api/endpoints.ts:133)
`apps/admin/src/shared/api/endpoints.ts:133` calls `PATCH /admin/tournaments/${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/tournaments/<p>` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/tasks (apps/admin/src/shared/api/endpoints.ts:81)
`apps/admin/src/shared/api/endpoints.ts:81` calls `POST /admin/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/tasks` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/tasks/${id}/publish (apps/admin/src/shared/api/endpoints.ts:87)
`apps/admin/src/shared/api/endpoints.ts:87` calls `POST /admin/tasks/${id}/publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/tasks/<p>/publish` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/tasks/${id}/reject (apps/admin/src/shared/api/endpoints.ts:90)
`apps/admin/src/shared/api/endpoints.ts:90` calls `POST /admin/tasks/${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/tasks/<p>/reject` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/tournaments (apps/admin/src/shared/api/endpoints.ts:130)
`apps/admin/src/shared/api/endpoints.ts:130` calls `POST /admin/tournaments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/tournaments` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/tournaments/${id}/grant-entry (apps/admin/src/shared/api/endpoints.ts:139)
`apps/admin/src/shared/api/endpoints.ts:139` calls `POST /admin/tournaments/${id}/grant-entry` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/tournaments/<p>/grant-entry` If this points at an external…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/users/${id}/ban (apps/admin/src/shared/api/endpoints.ts:110)
`apps/admin/src/shared/api/endpoints.ts:110` calls `POST /admin/users/${id}/ban` 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>/ban` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/users/${id}/grant-pro (apps/admin/src/shared/api/endpoints.ts:116)
`apps/admin/src/shared/api/endpoints.ts:116` calls `POST /admin/users/${id}/grant-pro` 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>/grant-pro` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/users/${id}/revoke-pro (apps/admin/src/shared/api/endpoints.ts:119)
`apps/admin/src/shared/api/endpoints.ts:119` calls `POST /admin/users/${id}/revoke-pro` 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>/revoke-pro` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/users/${id}/unban (apps/admin/src/shared/api/endpoints.ts:113)
`apps/admin/src/shared/api/endpoints.ts:113` calls `POST /admin/users/${id}/unban` 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>/unban` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /ai/review/${duelId} (apps/web/src/shared/api/endpoints.ts:227)
`apps/web/src/shared/api/endpoints.ts:227` calls `POST /ai/review/${duelId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/review/<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: POST /auth/login (apps/admin/src/shared/api/client.test.ts:101)
`apps/admin/src/shared/api/client.test.ts:101` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/login (apps/admin/src/shared/api/endpoints.ts:30)
`apps/admin/src/shared/api/endpoints.ts:30` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` 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 /auth/login (apps/web/src/shared/api/client.test.ts:156)
`apps/web/src/shared/api/client.test.ts:156` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` 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: POST /auth/login (apps/web/src/shared/api/endpoints.ts:90)
`apps/web/src/shared/api/endpoints.ts:90` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/logout (apps/admin/src/shared/api/endpoints.ts:37)
`apps/admin/src/shared/api/endpoints.ts:37` calls `POST /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/logout (apps/web/src/shared/api/endpoints.ts:97)
`apps/web/src/shared/api/endpoints.ts:97` calls `POST /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` 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 /auth/refresh (apps/admin/src/shared/api/endpoints.ts:41)
`apps/admin/src/shared/api/endpoints.ts:41` calls `POST /auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/refresh` 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: POST /auth/refresh (apps/web/src/shared/api/endpoints.ts:101)
`apps/web/src/shared/api/endpoints.ts:101` calls `POST /auth/refresh` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/refresh` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/register (apps/web/src/shared/api/endpoints.ts:62)
`apps/web/src/shared/api/endpoints.ts:62` calls `POST /auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/register` 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: POST /auth/resend-code (apps/web/src/shared/api/endpoints.ts:83)
`apps/web/src/shared/api/endpoints.ts:83` calls `POST /auth/resend-code` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/resend-code` 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: POST /auth/telegram (apps/web/src/shared/api/endpoints.ts:139)
`apps/web/src/shared/api/endpoints.ts:139` calls `POST /auth/telegram` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/telegram` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/telegram/register (apps/web/src/shared/api/endpoints.ts:147)
`apps/web/src/shared/api/endpoints.ts:147` calls `POST /auth/telegram/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/telegram/register` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/verify-email (apps/web/src/shared/api/endpoints.ts:69)
`apps/web/src/shared/api/endpoints.ts:69` calls `POST /auth/verify-email` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/verify-email` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/verify-link (apps/web/src/shared/api/endpoints.ts:76)
`apps/web/src/shared/api/endpoints.ts:76` calls `POST /auth/verify-link` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/verify-link` 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: POST /tournaments/${id}/answer (apps/web/src/shared/api/endpoints.ts:306)
`apps/web/src/shared/api/endpoints.ts:306` calls `POST /tournaments/${id}/answer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<p>/answer` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /tournaments/${id}/enter (apps/web/src/shared/api/endpoints.ts:299)
`apps/web/src/shared/api/endpoints.ts:299` calls `POST /tournaments/${id}/enter` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tournaments/<p>/enter` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /admin/feature-flags/${key} (apps/admin/src/shared/api/endpoints.ts:151)
`apps/admin/src/shared/api/endpoints.ts:151` calls `PUT /admin/feature-flags/${key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/feature-flags/<p>` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI PATCH `update_task` without auth dependency — apps/api/src/admin/router.py:74
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/admin/router.py:74 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_tournament` without auth dependency — apps/api/src/tournaments/admin_router.py:51
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/tournaments/admin_router.py:51 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_duel` without auth dependency — apps/api/src/internal_api/router.py:46
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/internal_api/router.py:46 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_tournament` without auth dependency — apps/api/src/tournaments/admin_router.py:35
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/tournaments/admin_router.py:35 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `finish_duel` without auth dependency — apps/api/src/internal_api/router.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/internal_api/router.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `grant_entry` without auth dependency — apps/api/src/tournaments/admin_router.py:60
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/tournaments/admin_router.py:60 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `publish_task` without auth dependency — apps/api/src/admin/router.py:84
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/admin/router.py:84 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recompute_places` without auth dependency — apps/api/src/tournaments/admin_router.py:72
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/tournaments/admin_router.py:72 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh` without auth dependency — apps/api/src/auth/router.py:202
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:202 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resend_code` without auth dependency — apps/api/src/auth/router.py:187
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:187 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_duel_share_card` without auth dependency — apps/api/src/internal_api/router.py:84
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/internal_api/router.py:84 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_auth` without auth dependency — apps/api/src/auth/router.py:77
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:77 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_redeem` without auth dependency — apps/api/src/internal_api/router.py:130
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/internal_api/router.py:130 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_register` without auth dependency — apps/api/src/auth/router.py:106
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:106 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_email` without auth dependency — apps/api/src/auth/router.py:148
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:148 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_link` without auth dependency — apps/api/src/auth/router.py:162
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/auth/router.py:162 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `write_ai_review` without auth dependency — apps/api/src/internal_api/router.py:113
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/internal_api/router.py:113 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `upsert_flag` without auth dependency — apps/api/src/admin/router.py:185
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/src/admin/router.py:185 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/admin/src/shared/api/client.ts:99
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/web/src/shared/api/client.ts:99
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. 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: apps/admin/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: apps/web/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 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/setup-uv@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 8 locations
.github/workflows/deploy.yml:51, 58, 74 (3 hits)
.github/workflows/api-ci.yml:65
.github/workflows/bot-ci.yml:29
.github/workflows/realtime-ci.yml:44
.github/workflows/web-ci.yml:37
.github/workflows/workers-ci.yml:32
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 'vue_v_html' in apps/web/src/pages/AiReviewPage.vue:60
Found a known-risky pattern (vue_v_html). Review and replace if possible.
apps/web/src/pages/AiReviewPage.vue:60 Vue v html
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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.27-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/admin/Dockerfile:25 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:1.27-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
apps/web/Dockerfile:29 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 5 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 5 locations
apps/realtime/Dockerfile:6, 14, 25 (3 hits)
apps/admin/Dockerfile:6
apps/web/Dockerfile:6
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 6 occurrences 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.
3 files, 6 locations
apps/api/Dockerfile:6, 24 (2 hits)
apps/bot/Dockerfile:4, 20 (2 hits)
apps/workers/Dockerfile:5, 25 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 7 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.
5 files, 7 locations
.github/workflows/realtime-ci.yml:40, 47 (2 hits)
.github/workflows/web-ci.yml:33, 40 (2 hits)
.github/workflows/api-ci.yml:62
.github/workflows/bot-ci.yml:27
.github/workflows/workers-ci.yml:29
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: apps/api/src/duels/repository.py:get, apps/api/src/ai_review/repository.py:get_duel 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.
4 occurrences
repo-level (4 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: apps/bot/src/bot/inline_store.py:aclose, apps/workers/src/workers/dedup.py:aclose, apps/workers/src/workers/inline_store.py:aclose This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/admin/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/admin/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/realtime/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/realtime/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/contracts/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/contracts/package.json LockfileReproducibilityGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: create_checkout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/src/billing/providers/base.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: create_checkout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/src/billing/providers/manual.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: needs_rehash
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/src/core/security.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: request_stop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/workers/src/workers/ai_review.py:235
low System graph software Dead code conf 1.00 Possibly dead Python function: request_stop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/workers/src/workers/image_gen.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: send_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/workers/src/workers/telegram_client.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: telegram_by_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/workers/src/workers/internal_client.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: to_payload
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/src/core/errors.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: weekly_key_for_date
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/src/leaderboard/keys.py:27
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 — apps/web/src/pages/LandingPage.vue:100
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: GET /
`apps/api/src/tournaments/router.py` declares `GET /` 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 /daily/leaderboard
`apps/api/src/daily/router.py` declares `GET /daily/leaderboard` 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 /duels/{duel_id}/card
`apps/api/src/internal_api/router.py` declares `GET /duels/{duel_id}/card` 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 /duels/{duel_id}/review-data
`apps/api/src/internal_api/router.py` declares `GET /duels/{duel_id}/review-data` 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 /feature-flags
`apps/api/src/admin/router.py` declares `GET /feature-flags` 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 /leaderboard
`apps/api/src/leaderboard/router.py` declares `GET /leaderboard` 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 /leaderboard/me
`apps/api/src/leaderboard/router.py` declares `GET /leaderboard/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 /me/duels
`apps/api/src/users/router.py` declares `GET /me/duels` 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 /me/stats
`apps/api/src/users/router.py` declares `GET /me/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 /share/{duel_id}
`apps/api/src/duels/router.py` declares `GET /share/{duel_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 /tasks
`apps/api/src/admin/router.py` declares `GET /tasks` 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 /telegram/by-user/{user_id}
`apps/api/src/internal_api/router.py` declares `GET /telegram/by-user/{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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /telegram/user/{telegram_user_id}
`apps/api/src/internal_api/router.py` declares `GET /telegram/user/{telegram_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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users
`apps/api/src/admin/router.py` declares `GET /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 /widget/{username}.svg
`apps/api/src/telegram/router.py` declares `GET /widget/{username}.svg` 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 /{duel_id}
`apps/api/src/ai_review/router.py` declares `GET /{duel_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 /{tournament_id}
`apps/api/src/tournaments/router.py` declares `GET /{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: GET /{tournament_id}/tasks
`apps/api/src/tournaments/router.py` declares `GET /{tournament_id}/tasks` 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 /tasks/{task_id}
`apps/api/src/admin/router.py` declares `PATCH /tasks/{task_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: PATCH /{tournament_id}
`apps/api/src/tournaments/admin_router.py` declares `PATCH /{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: POST /
`apps/api/src/tournaments/admin_router.py` declares `POST /` 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 /ai-reviews/{duel_id}/{user_id}
`apps/api/src/internal_api/router.py` declares `POST /ai-reviews/{duel_id}/{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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /duels
`apps/api/src/internal_api/router.py` declares `POST /duels` 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 /duels/{duel_id}/finish
`apps/api/src/internal_api/router.py` declares `POST /duels/{duel_id}/finish` 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 /duels/{duel_id}/share-card
`apps/api/src/internal_api/router.py` declares `POST /duels/{duel_id}/share-card` 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: POST /login
`apps/api/src/auth/router.py` declares `POST /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 /logout
`apps/api/src/auth/router.py` declares `POST /logout` 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 /me/avatar/confirm
`apps/api/src/users/router.py` declares `POST /me/avatar/confirm` 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 /me/avatar/presign
`apps/api/src/users/router.py` declares `POST /me/avatar/presign` 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 /refresh
`apps/api/src/auth/router.py` declares `POST /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 /register
`apps/api/src/auth/router.py` declares `POST /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 /resend-code
`apps/api/src/auth/router.py` declares `POST /resend-code` 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 /tasks
`apps/api/src/admin/router.py` declares `POST /tasks` 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 /tasks/{task_id}/publish
`apps/api/src/admin/router.py` declares `POST /tasks/{task_id}/publish` 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 /tasks/{task_id}/reject
`apps/api/src/admin/router.py` declares `POST /tasks/{task_id}/reject` 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 /telegram
`apps/api/src/auth/router.py` declares `POST /telegram` 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 /telegram/redeem
`apps/api/src/internal_api/router.py` declares `POST /telegram/redeem` 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 /telegram/register
`apps/api/src/auth/router.py` declares `POST /telegram/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 /users/{user_id}/ban
`apps/api/src/admin/router.py` declares `POST /users/{user_id}/ban` 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 /users/{user_id}/grant-pro
`apps/api/src/admin/router.py` declares `POST /users/{user_id}/grant-pro` 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 /users/{user_id}/revoke-pro
`apps/api/src/admin/router.py` declares `POST /users/{user_id}/revoke-pro` 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 /users/{user_id}/unban
`apps/api/src/admin/router.py` declares `POST /users/{user_id}/unban` 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 /verify-email
`apps/api/src/auth/router.py` declares `POST /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: POST /verify-link
`apps/api/src/auth/router.py` declares `POST /verify-link` 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 /{duel_id}
`apps/api/src/ai_review/router.py` declares `POST /{duel_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: POST /{tournament_id}/answer
`apps/api/src/tournaments/router.py` declares `POST /{tournament_id}/answer` 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 /{tournament_id}/enter
`apps/api/src/tournaments/router.py` declares `POST /{tournament_id}/enter` 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 /{tournament_id}/grant-entry
`apps/api/src/tournaments/admin_router.py` declares `POST /{tournament_id}/grant-entry` 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 /{tournament_id}/recompute-places
`apps/api/src/tournaments/admin_router.py` declares `POST /{tournament_id}/recompute-places` 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 /feature-flags/{key}
`apps/api/src/admin/router.py` declares `PUT /feature-flags/{key}` 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: packages/contracts/src/api-types.ts (3145 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/059ac544-1868-4079-a978-6110e61824cb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/059ac544-1868-4079-a978-6110e61824cb/

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.