high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/${cat.endpoint}?season=${SEASON}&min_bf=80&sort_by=${cat.sort}&sort_dir=desc&limit=2 (frontend/src/pages/FreeHomepage.jsx:432)

`frontend/src/pages/FreeHomepage.jsx:432` calls `GET /api/v1/leaderboards/${cat.endpoint}?season=${SEASON}&min_bf=80&sort_by=${cat.sort}&sort_dir=desc&limit=2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leade…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/${endpoint}?season=${SEASON}&sort_by=${sortBy}&sort_dir=desc&limit=200&qualified=true (frontend/src/pages/PremiumHomepage.jsx:136)

`frontend/src/pages/PremiumHomepage.jsx:136` calls `GET /api/v1/leaderboards/${endpoint}?season=${SEASON}&sort_by=${sortBy}&sort_dir=desc&limit=200&qualified=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/l…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/fielding?${qs} (frontend/src/pages/FieldingLeaderboard.jsx:149)

`frontend/src/pages/FieldingLeaderboard.jsx:149` calls `GET /api/v1/leaderboards/fielding?${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leaderboards/fielding` If this points at an external API, prefix it …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/fielding?season=${SEASON}&position=SS&division_id=4&min_games=10&limit=3 (frontend/src/pages/AnonymousHomepage.jsx:438)

`frontend/src/pages/AnonymousHomepage.jsx:438` calls `GET /api/v1/leaderboards/fielding?season=${SEASON}&position=SS&division_id=4&min_games=10&limit=3` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leaderboards…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/percentiles?season=${SEASON}&limit=60 (frontend/src/pages/FreeHomepage.jsx:529)

`frontend/src/pages/FreeHomepage.jsx:529` calls `GET /api/v1/leaderboards/percentiles?season=${SEASON}&limit=60` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leaderboards/percentiles` If this points at an exter…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/relievers?${qs} (frontend/src/pages/RelieverLeaderboard.jsx:103)

`frontend/src/pages/RelieverLeaderboard.jsx:103` calls `GET /api/v1/leaderboards/relievers?${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leaderboards/relievers` If this points at an external API, prefix i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/leaderboards/war?${params} (frontend/src/pages/WarLeaderboard.jsx:152)

`frontend/src/pages/WarLeaderboard.jsx:152` calls `GET /api/v1/leaderboards/war?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/leaderboards/war` If this points at an external API, prefix it with `https…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/national-rankings?season=${season} (frontend/src/pages/PlayerGraphic.jsx:476)

`frontend/src/pages/PlayerGraphic.jsx:476` calls `GET /api/v1/national-rankings?season=${season}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/national-rankings` If this points at an external API, prefix it wit…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/players/${playerId} (frontend/src/pages/DraftBoard.jsx:98)

`frontend/src/pages/DraftBoard.jsx:98` calls `GET /api/v1/players/${playerId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/players/` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/players/${playerId}/streaks?season=${season} (frontend/src/components/playerProfile/shared.jsx:571)

`frontend/src/components/playerProfile/shared.jsx:571` calls `GET /api/v1/players/${playerId}/streaks?season=${season}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/players//streaks` If this points at an ext…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/players/${playerId}/streaks?season=${season} (frontend/src/pages/PlayerDetail.jsx:1412)

`frontend/src/pages/PlayerDetail.jsx:1412` calls `GET /api/v1/players/${playerId}/streaks?season=${season}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/players//streaks` If this points at an external API, p…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/players/search?q=${encodeURIComponent(query)} (frontend/src/pages/PlayerGraphic.jsx:205)

`frontend/src/pages/PlayerGraphic.jsx:205` calls `GET /api/v1/players/search?q=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/players/search` If this points at an external API, prefi…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/pro-alumni (frontend/src/pages/ProTracker.jsx:59)

`frontend/src/pages/ProTracker.jsx:59` calls `GET /api/v1/pro-alumni` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/pro-alumni` If this points at an external API, prefix it with `https://` so the matcher skips i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/quiz/league-question?season=${SEASON} (frontend/src/pages/FreeHomepage.jsx:634)

`frontend/src/pages/FreeHomepage.jsx:634` calls `GET /api/v1/quiz/league-question?season=${SEASON}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/quiz/league-question` If this points at an external API, prefix i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/recruiting/freshman-by-division?season=${CURRENT_SEASON} (frontend/src/pages/RecruitingTips.jsx:38)

`frontend/src/pages/RecruitingTips.jsx:38` calls `GET /api/v1/recruiting/freshman-by-division?season=${CURRENT_SEASON}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/recruiting/freshman-by-division` If this poin…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/recruiting/nwac-advancement?season=${CURRENT_SEASON} (frontend/src/pages/NwacAdvancement.jsx:44)

`frontend/src/pages/NwacAdvancement.jsx:44` calls `GET /api/v1/recruiting/nwac-advancement?season=${CURRENT_SEASON}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/recruiting/nwac-advancement` If this points at a…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/recruiting/program-guide (frontend/src/pages/RecruitingProgramGuide.jsx:28)

`frontend/src/pages/RecruitingProgramGuide.jsx:28` calls `GET /api/v1/recruiting/program-guide` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/recruiting/program-guide` If this points at an external API, prefix i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/search?q=${encodeURIComponent(q)}&limit=6 (frontend/src/components/Header.jsx:205)

`frontend/src/components/Header.jsx:205` calls `GET /api/v1/search?q=${encodeURIComponent(q)}&limit=6` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/search` If this points at an external API, prefix it with `htt…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/site-stats (frontend/src/pages/About.jsx:1450)

`frontend/src/pages/About.jsx:1450` calls `GET /api/v1/site-stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/site-stats` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/site-stats (frontend/src/pages/AnonymousHomepage.jsx:121)

`frontend/src/pages/AnonymousHomepage.jsx:121` calls `GET /api/v1/site-stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/site-stats` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/stats/last-updated (frontend/src/components/StatsLastUpdated.jsx:63)

`frontend/src/components/StatsLastUpdated.jsx:63` calls `GET /api/v1/stats/last-updated` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/stats/last-updated` If this points at an external API, prefix it with `https…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/summer/leaderboards/${c.side}?${params} (frontend/src/components/home/StatWidgets.jsx:299)

`frontend/src/components/home/StatWidgets.jsx:299` calls `GET /api/v1/summer/leaderboards/${c.side}?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/summer/leaderboards/` If this points at an external…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/team-ratings?season=${season} (frontend/src/pages/PlayerGraphic.jsx:475)

`frontend/src/pages/PlayerGraphic.jsx:475` calls `GET /api/v1/team-ratings?season=${season}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/team-ratings` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/teams/${teamId}/championships (frontend/src/pages/TeamDetail.jsx:358)

`frontend/src/pages/TeamDetail.jsx:358` calls `GET /api/v1/teams/${teamId}/championships` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/teams//championships` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/teams/scatter?season=${SEASON}&x_stat=${combo.x}&y_stat=${combo.y} (frontend/src/pages/FreeHomepage.jsx:118)

`frontend/src/pages/FreeHomepage.jsx:118` calls `GET /api/v1/teams/scatter?season=${SEASON}&x_stat=${combo.x}&y_stat=${combo.y}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/teams/scatter` If this points at an …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/teams/scatter?season=${SEASON}&x_stat=${stat.key}&y_stat=win_pct (frontend/src/pages/FreeHomepage.jsx:257)

`frontend/src/pages/FreeHomepage.jsx:257` calls `GET /api/v1/teams/scatter?season=${SEASON}&x_stat=${stat.key}&y_stat=win_pct` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/teams/scatter` If this points at an ex…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/coaching/lineup-helper/build (frontend/src/pages/LineupHelper.jsx:829)

`frontend/src/pages/LineupHelper.jsx:829` calls `POST /api/v1/coaching/lineup-helper/build` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/coaching/lineup-helper/build` If this points at an external API, prefix i…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/coaching/lineup-helper/override (frontend/src/pages/LineupHelper.jsx:85)

`frontend/src/pages/LineupHelper.jsx:85` calls `POST /api/v1/coaching/lineup-helper/override` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/coaching/lineup-helper/override` If this points at an external API, pre…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/feature-requests (frontend/src/pages/FeatureRequest.jsx:27)

`frontend/src/pages/FeatureRequest.jsx:27` calls `POST /api/v1/feature-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/feature-requests` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/v1/recruiting/programs/${teamId} (frontend/src/pages/RecruitingGuide.jsx:210)

`frontend/src/pages/RecruitingGuide.jsx:210` calls `PUT /api/v1/recruiting/programs/${teamId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/recruiting/programs/` If this points at an external API, prefix it …

Dangling fetchFetch

high System graph security auth conf 1.00 FastAPI POST `grid_check_custom` without auth dependency — backend/app/api/grid.py:1047

`@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/app/api/grid.py:1047 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `grid_solutions` without auth dependency — backend/app/api/grid.py:1064

`@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/app/api/grid.py:1064 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `grid_validate_custom` without auth dependency — backend/app/api/grid.py:1132

`@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/app/api/grid.py:1132 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `lineup_helper_build` without auth dependency — backend/app/api/coaching_tools.py:1463

`@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/app/api/coaching_tools.py:1463 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `lineup_helper_manual` without auth dependency — backend/app/api/coaching_tools.py:1166

`@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/app/api/coaching_tools.py:1166 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `lineup_helper_override` without auth dependency — backend/app/api/coaching_tools.py:1505

`@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/app/api/coaching_tools.py:1505 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `one_click_unsubscribe` without auth dependency — backend/app/api/email_prefs.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.

backend/app/api/email_prefs.py:202 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — backend/app/api/billing.py:565

`@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/app/api/billing.py:565 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `submit_feature_request` without auth dependency — backend/app/api/feature_requests.py:153

`@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/app/api/feature_requests.py:153 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI PUT `update_prefs_by_token` without auth dependency — backend/app/api/email_prefs.py:169

`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

backend/app/api/email_prefs.py:169 securityAuth fastapi unauth mutation

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/api/img.ts:104

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 — frontend/src/components/home/StatWidgets.jsx:13

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 — frontend/src/hooks/useApi.js:62

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 — frontend/src/hooks/useArticles.js:100

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 — frontend/src/hooks/useTier.js:70

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 — frontend/src/pages/Account.jsx:65

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 — frontend/src/pages/BattingLeaderboard.jsx:133

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 — frontend/src/pages/FieldingLeaderboard.jsx:149

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 — frontend/src/pages/FreeHomepage.jsx:257

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 — frontend/src/pages/PitchingLeaderboard.jsx:133

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 — frontend/src/pages/PremiumHomepage.jsx:157

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 — frontend/src/pages/Pricing.jsx:243

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 — frontend/src/pages/RelieverLeaderboard.jsx:103

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 — frontend/src/pages/StandingsPage.jsx:288

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 — frontend/src/pages/TeamComparison.jsx:310

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 — frontend/src/pages/TeamInfoGraphic.jsx:887

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 — frontend/src/pages/Unsubscribe.jsx:32

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 — frontend/src/pages/WarLeaderboard.jsx:152

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 — frontend/src/pages/WclRecapGraphic.jsx:333

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 license. 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 quality Integrity conf 1.00 33 occurrences Frontend route `/summer/teams/:id` has no Link/navigate to it — frontend/src/App.jsx

The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.

33 occurrences

repo-level (33 hits)

Orphan pageWiring

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in frontend/api/img.ts:144

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

frontend/api/img.ts:144 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/signature.html:230

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/public/signature.html:230 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pages/RecruitingMap.jsx:178

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/src/pages/RecruitingMap.jsx:178 Direct innerhtml assignment

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/archive/scrape_browser_stats.py:613

`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/generate_social_graphic.py:462

`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 146 placeholder/mock markers across 68 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

13 test file(s) for 519 source file(s) (ratio 0.03). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 29 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `ADMIN_EMAILS`, `ARTICLE_AUTHOR_EMAILS`, `DATABASE_URL`, `DB_POOL_MAX`, `EMAIL_FROM`, `LEVELS`, `MODE`, `PNW_BASEBALL_DB` + 21 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 1612 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 quality Integrity conf 1.00 Near-duplicate function bodies in 11 places

Functions with the same first-5-line body hash: scripts/dedup_games.py:get_conn, scripts/dedup_game_pitching.py:get_conn, scripts/backfill_wmt_boxscores.py:get_conn, scripts/dedup_game_batting.py:get_conn This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw…

duplicatesduplication

low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: scripts/parse_nwac_boxscore.py:get_stat, scripts/parse_nwac_boxscore.py:get_stat 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.

7 occurrences

repo-level (7 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: scripts/scrape_naia.py:safe_int, scripts/scrape_nwac.py:safe_int, scripts/archive/scrape_browser_stats.py:safe_int This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…

3 occurrences

repo-level (3 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: scripts/scrape_naia.py:fetch_page, scripts/scrape_d3.py:fetch_page, scripts/scrape_d2.py:fetch_page, scripts/scrape_d1.py:fetch_page This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Co…

7 occurrences

repo-level (7 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places

Functions with the same first-5-line body hash: scripts/scrape_naia.py:fetch_json, scripts/scrape_boxscores.py:fetch_json, scripts/scrape_d3.py:fetch_json, scripts/scrape_d2.py:fetch_json This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygie…

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places

Functions with the same first-5-line body hash: scripts/retry_missing_boxscores.py:resolve_team, scripts/wipe_team_batting.py:resolve_team, scripts/force_rescrape_one_game.py:resolve_team, scripts/archive/inspect_one_game_batting.py:resolve_team This is *the* AI-coder failure mode (4× more duplica…

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 Integrity conf 1.00 Old/deprecated-named symbol `_parse_sidearm_schedule_v2` in scripts/scrape_boxscores.py:746

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 `affiliated_team_v1` in frontend/src/context/AffiliationContext.jsx:17

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 `nwbb_v1` in scripts/projections/backtest.py:18

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 `nwbb_v1` in scripts/projections/team_projection.py:6

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 `pc_legacy` in scripts/parse_pbp_events.py:338

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 `pc_legacy` in scripts/parse_pbp_hr.py:163

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 `ps_old` in scripts/resync_pitching_stats_from_boxscores.py:8

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 `tier_cache_v1` in frontend/src/hooks/useTier.js:27

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: add_stats_grid

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/recruiting_book/build_docx.py:204

low System graph software Dead code conf 1.00 Possibly dead Python function: afterFlowable

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/recruiting_book/build_book.py:2606

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/app/cache.py:45

low System graph software Dead code conf 1.00 Possibly dead Python function: draw

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/recruiting_book/build_book.py:1054

low System graph software Dead code conf 1.00 Possibly dead Python function: explain

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:409

low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_one

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/archive/scan_pbp_coverage.py:72

low System graph software Dead code conf 1.00 Possibly dead Python function: norm_class

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/projections/derive_constants.py:50

low System graph software Dead code conf 1.00 Possibly dead Python function: norm_year

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/fill_player_bio_from_csv.py:37

low System graph software Dead code conf 1.00 Possibly dead Python function: pos_factor

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/projections/write_projections_db.py:290

low System graph software Dead code conf 1.00 Possibly dead Python function: render

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/main.py:55

low System graph software Dead code conf 1.00 Possibly dead Python function: scrape_massey_ratings

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/scrape_national_ratings.py:317

low System graph software Dead code conf 1.00 Possibly dead Python function: scrape_nwac_standings

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/scrape_records.py:135

low System graph software Dead code conf 1.00 Possibly dead Python function: spray_for

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/classify_batted_ball.py:369

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_avg

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:480

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_doubles

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:442

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_hits

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:437

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_hr

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:427

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_obp

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:486

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_owar

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:472

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_pa

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:467

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_rbi

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:432

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_runs

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:462

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_sb

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:452

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_slg

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:492

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_triples

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:447

low System graph software Dead code conf 1.00 Possibly dead Python function: t_leader_walks

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/app/api/quiz.py:457

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/pages/KeyMatchupGraphic.jsx:537

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/gm/generate_non_naia_teams.js:430

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 /

`backend/app/main.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 /conference-standings-graphic

`backend/app/api/routes.py` declares `GET /conference-standings-graphic` 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 /conferences

`backend/app/api/routes.py` declares `GET /conferences` 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 /divisions

`backend/app/api/routes.py` declares `GET /divisions` 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 /feature-requests

`backend/app/api/feature_requests.py` declares `GET /feature-requests` 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 /games/upset-of-the-day

`backend/app/api/routes.py` declares `GET /games/upset-of-the-day` 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 /games/win-probabilities

`backend/app/api/routes.py` declares `GET /games/win-probabilities` 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 /hometown-search

`backend/app/api/routes.py` declares `GET /hometown-search` 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 /leaderboards/batting

`backend/app/api/routes.py` declares `GET /leaderboards/batting` 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 /leaderboards/batting-pbp

`backend/app/api/routes.py` declares `GET /leaderboards/batting-pbp` 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 /leaderboards/clubs

`backend/app/api/routes.py` declares `GET /leaderboards/clubs` 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 /leaderboards/fielding

`backend/app/api/routes.py` declares `GET /leaderboards/fielding` 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 /leaderboards/percentiles

`backend/app/api/routes.py` declares `GET /leaderboards/percentiles` 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 /leaderboards/pitching

`backend/app/api/routes.py` declares `GET /leaderboards/pitching` 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 /leaderboards/pitching-pbp

`backend/app/api/routes.py` declares `GET /leaderboards/pitching-pbp` 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 /leaderboards/relievers

`backend/app/api/routes.py` declares `GET /leaderboards/relievers` 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 /leaderboards/team-batting-pbp

`backend/app/api/routes.py` declares `GET /leaderboards/team-batting-pbp` 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 /leaderboards/team-pitching-pbp

`backend/app/api/routes.py` declares `GET /leaderboards/team-pitching-pbp` 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 /leaderboards/teams

`backend/app/api/routes.py` declares `GET /leaderboards/teams` 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 /leaderboards/war

`backend/app/api/routes.py` declares `GET /leaderboards/war` 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 /league-question

`backend/app/api/quiz.py` declares `GET /league-question` 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/affiliated-team

`backend/app/api/account.py` declares `GET /me/affiliated-team` 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/subscription

`backend/app/api/account.py` declares `GET /me/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: GET /national-rankings

`backend/app/api/routes.py` declares `GET /national-rankings` 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 /nwac-championship-odds

`backend/app/api/routes.py` declares `GET /nwac-championship-odds` 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 /nwac-mvp-tracker

`backend/app/api/routes.py` declares `GET /nwac-mvp-tracker` 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 /players/{player_id}/goose-eggs

`backend/app/api/routes.py` declares `GET /players/{player_id}/goose-eggs` 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 /playoff-projections

`backend/app/api/routes.py` declares `GET /playoff-projections` 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 /question

`backend/app/api/quiz.py` declares `GET /question` 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 /questions

`backend/app/api/quiz.py` declares `GET /questions` 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 /records

`backend/app/api/routes.py` declares `GET /records` 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 /search

`backend/app/api/routes.py` declares `GET /search` 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 /site-stats

`backend/app/api/routes.py` declares `GET /site-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 /standings

`backend/app/api/routes.py` declares `GET /standings` 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 /stat-leaders

`backend/app/api/routes.py` declares `GET /stat-leaders` 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 /stats/last-updated

`backend/app/api/routes.py` declares `GET /stats/last-updated` 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 /team-ratings

`backend/app/api/routes.py` declares `GET /team-ratings` 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 /teams

`backend/app/api/routes.py` declares `GET /teams` 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 /teams/compare

`backend/app/api/routes.py` declares `GET /teams/compare` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /teams/correlations

`backend/app/api/routes.py` declares `GET /teams/correlations` 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 /teams/matchup

`backend/app/api/routes.py` declares `GET /teams/matchup` 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 /teams/scatter

`backend/app/api/routes.py` declares `GET /teams/scatter` 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 /teams/summary

`backend/app/api/routes.py` declares `GET /teams/summary` 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 /teams/{team_id}

`backend/app/api/routes.py` declares `GET /teams/{team_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 /teams/{team_id}/info-graphic

`backend/app/api/routes.py` declares `GET /teams/{team_id}/info-graphic` 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 /teams/{team_id}/rankings

`backend/app/api/routes.py` declares `GET /teams/{team_id}/rankings` 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 /teams/{team_id}/season-recap

`backend/app/api/routes.py` declares `GET /teams/{team_id}/season-recap` 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 /{full_path:path}

`backend/app/main.py` declares `GET /{full_path:path}` 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 /feature-requests

`backend/app/api/feature_requests.py` declares `POST /feature-requests` 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 /me/affiliated-team

`backend/app/api/account.py` declares `PUT /me/affiliated-team` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: backend/app/api/coaching_tools.py (1647 lines)