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

WestsideSage/Dodger

https://github.com/WestsideSage/Dodger · scanned 2026-06-16 00:56 UTC (2 months, 1 week ago)

233 raw signals (0 security + 233 graph)

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

Complete repo analysis

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

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

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

high System graph security auth conf 1.00 FastAPI POST `acknowledge_match_report` without auth dependency — src/dodgeball_sim/server.py:1019
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1019 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `advance_offseason_beat` without auth dependency — src/dodgeball_sim/server.py:1163
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1163 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_build_from_scratch` without auth dependency — src/dodgeball_sim/server.py:1083
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1083 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_delete_save` without auth dependency — src/dodgeball_sim/server.py:1121
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1121 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_load_save` without auth dependency — src/dodgeball_sim/server.py:1098
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1098 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_new_save` without auth dependency — src/dodgeball_sim/server.py:1052
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1052 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_unload_save` without auth dependency — src/dodgeball_sim/server.py:1133
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1133 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `auto_assign_lineup` without auth dependency — src/dodgeball_sim/server.py:841
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:841 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `confirm_lineup` without auth dependency — src/dodgeball_sim/server.py:736
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:736 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_recruiting_promise` without auth dependency — src/dodgeball_sim/server.py:771
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:771 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fast_forward_command_center` without auth dependency — src/dodgeball_sim/server.py:873
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:873 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `hire_dynasty_staff` without auth dependency — src/dodgeball_sim/server.py:781
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:781 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `offseason_begin_season` without auth dependency — src/dodgeball_sim/server.py:1183
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1183 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `offseason_recruit` without auth dependency — src/dodgeball_sim/server.py:1171
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:1171 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_roster_release` without auth dependency — src/dodgeball_sim/server.py:652
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:652 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recruiting_contact` without auth dependency — src/dodgeball_sim/server.py:964
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:964 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recruiting_pitch_angle` without auth dependency — src/dodgeball_sim/server.py:974
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:974 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recruiting_scout` without auth dependency — src/dodgeball_sim/server.py:959
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:959 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recruiting_sign` without auth dependency — src/dodgeball_sim/server.py:985
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:985 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recruiting_visit` without auth dependency — src/dodgeball_sim/server.py:969
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:969 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_command_center_plan` without auth dependency — src/dodgeball_sim/server.py:719
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:719 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `scout_opponent` without auth dependency — src/dodgeball_sim/server.py:727
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:727 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_lineup_auto_reorder` without auth dependency — src/dodgeball_sim/server.py:824
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:824 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_command_center_week` without auth dependency — src/dodgeball_sim/server.py:855
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:855 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_command` without auth dependency — src/dodgeball_sim/server.py:900
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:900 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_week` without auth dependency — src/dodgeball_sim/server.py:908
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:908 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `skip_season_preview` without auth dependency — src/dodgeball_sim/server.py:745
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:745 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_lineup` without auth dependency — src/dodgeball_sim/server.py:801
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:801 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_tactics` without auth dependency — src/dodgeball_sim/server.py:791
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/dodgeball_sim/server.py:791 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/api/client.ts: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 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, ci. 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 Network/subprocess call without timeout or try/except — src/dodgeball_sim/web_cli.py:164
`subprocess.run(...)` 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 security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 16 placeholder/mock markers across 11 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 234 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/PlayerDetailModal.tsx:70
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: tools/v23_pyramid_smoke.py:walk_offseason, tools/climb_resistance_probe.py:walk_offseason 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/dodgeball_sim/official_adapter.py:run_generic, src/dodgeball_sim/rec_adapter.py:run, src/dodgeball_sim/rec_adapter.py:run_generic This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). C…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/dodgeball_sim/official_engine.py:run_scripted_game, src/dodgeball_sim/official_engine.py:run_autonomous_game, src/dodgeball_sim/official_engine.py:run_autonomous_match, src/dodgeball_sim/official_engine.py:run This is *the* AI-coder failure mode …
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 `_migrate_v1` in src/dodgeball_sim/persistence.py:236
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 `_migrate_v1` in tests/test_official_backward_compat.py:15
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 `_migrate_v1` in tests/test_persistence.py:13
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 `_migrate_v1` in tests/test_save_meta_nonmutating.py:26
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 `allow_legacy` in src/dodgeball_sim/save_service.py:20
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 `allow_legacy` in src/dodgeball_sim/server.py:239
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 `allow_legacy` in tests/test_server_save_boundary.py:210
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 `dashboard_copy` in tests/test_aftermath_payload.py:35
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 `dev_legacy` in tests/test_development.py:134
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `p_legacy` in tests/test_dynasty_progression_health.py:118
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `p_legacy` in tests/test_first_hour_growth_truth.py:139
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 `sanitize_dashboard_copy` in src/dodgeball_sim/command_week_service.py:395
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_has_unresolved_token_allows_normal_sports_copy` in tests/test_copy_quality.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_headline_without_moments_falls_back_to_margin_copy` in tests/test_voice_verdict_priority.py:44
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_inconclusive_draw_no_lever_is_honest_no_lever_not_loss_copy` in tests/test_manager_lesson.py:102
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_policy_line_uses_default_centroid_copy` in tests/test_voice_pregame.py:7
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_voice_register_endpoint_returns_tier1_copy` in tests/test_policy_api.py:107
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 `visible_copy` in tests/test_command_center.py:152
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 `visible_copy` in tests/test_server.py:321
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: announced_or_absent_sections
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/official_conformance_ledger.py:476
low System graph software Dead code conf 1.00 Possibly dead Python function: apply_ruleset
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/meta.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: enforced_sections
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/official_conformance_ledger.py:470
low System graph software Dead code conf 1.00 Possibly dead Python function: format_analysis_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/replay_service.py:729
low System graph software Dead code conf 1.00 Possibly dead Python function: format_event_details
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/replay_service.py:696
low System graph software Dead code conf 1.00 Possibly dead Python function: format_event_row
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/replay_service.py:690
low System graph software Dead code conf 1.00 Possibly dead Python function: is_eligible_for_catch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/player_state.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: is_in_queue
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/player_state.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: matchup_preview
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dodgeball_sim/matchup_details.py:184
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 — docs/archive/prototypes/claude-design/ui_kits/dodger-web-app/test-ui.js:9
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 — tests/e2e/naive_playtest_runner.spec.ts:25
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 — tests/e2e/v12_ai_program_managers.spec.ts:17
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: ANY /api/{full_path:path}
`src/dodgeball_sim/server.py` declares `ANY /api/{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: GET /api/command-center
`src/dodgeball_sim/server.py` declares `GET /api/command-center` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/command-center/history
`src/dodgeball_sim/server.py` declares `GET /api/command-center/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dynasty-office
`src/dodgeball_sim/server.py` declares `GET /api/dynasty-office` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/history/league
`src/dodgeball_sim/server.py` declares `GET /api/history/league` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/history/my-program
`src/dodgeball_sim/server.py` declares `GET /api/history/my-program` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/matches/{match_id}/highlights
`src/dodgeball_sim/server.py` declares `GET /api/matches/{match_id}/highlights` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/matches/{match_id}/replay
`src/dodgeball_sim/server.py` declares `GET /api/matches/{match_id}/replay` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/news
`src/dodgeball_sim/server.py` declares `GET /api/news` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/offseason/beat
`src/dodgeball_sim/server.py` declares `GET /api/offseason/beat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/playoffs/bracket
`src/dodgeball_sim/server.py` declares `GET /api/playoffs/bracket` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/roster
`src/dodgeball_sim/server.py` declares `GET /api/roster` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/save-state
`src/dodgeball_sim/server.py` declares `GET /api/save-state` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/saves
`src/dodgeball_sim/server.py` declares `GET /api/saves` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/saves/clubs
`src/dodgeball_sim/server.py` declares `GET /api/saves/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 /api/schedule
`src/dodgeball_sim/server.py` declares `GET /api/schedule` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/standings
`src/dodgeball_sim/server.py` declares `GET /api/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 /api/status
`src/dodgeball_sim/server.py` declares `GET /api/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/tactics
`src/dodgeball_sim/server.py` declares `GET /api/tactics` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/voice-register/{tier}
`src/dodgeball_sim/server.py` declares `GET /api/voice-register/{tier}` 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}
`src/dodgeball_sim/server.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 /api/command-center/confirm-lineup
`src/dodgeball_sim/server.py` declares `POST /api/command-center/confirm-lineup` 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: POST /api/command-center/fast-forward
`src/dodgeball_sim/server.py` declares `POST /api/command-center/fast-forward` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/command-center/plan
`src/dodgeball_sim/server.py` declares `POST /api/command-center/plan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/command-center/scout
`src/dodgeball_sim/server.py` declares `POST /api/command-center/scout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/command-center/season-preview/skip
`src/dodgeball_sim/server.py` declares `POST /api/command-center/season-preview/skip` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/command-center/simulate
`src/dodgeball_sim/server.py` declares `POST /api/command-center/simulate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/dynasty-office/promises
`src/dodgeball_sim/server.py` declares `POST /api/dynasty-office/promises` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/dynasty-office/staff/hire
`src/dodgeball_sim/server.py` declares `POST /api/dynasty-office/staff/hire` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/lineup
`src/dodgeball_sim/server.py` declares `POST /api/lineup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/lineup/auto-assign
`src/dodgeball_sim/server.py` declares `POST /api/lineup/auto-assign` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/lineup/auto-reorder
`src/dodgeball_sim/server.py` declares `POST /api/lineup/auto-reorder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/matches/{match_id}/acknowledge
`src/dodgeball_sim/server.py` declares `POST /api/matches/{match_id}/acknowledge` 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 /api/offseason/advance
`src/dodgeball_sim/server.py` declares `POST /api/offseason/advance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/offseason/begin-season
`src/dodgeball_sim/server.py` declares `POST /api/offseason/begin-season` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/offseason/recruit
`src/dodgeball_sim/server.py` declares `POST /api/offseason/recruit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recruiting/contact/{prospect_id}
`src/dodgeball_sim/server.py` declares `POST /api/recruiting/contact/{prospect_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recruiting/pitch-angle
`src/dodgeball_sim/server.py` declares `POST /api/recruiting/pitch-angle` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recruiting/scout/{prospect_id}
`src/dodgeball_sim/server.py` declares `POST /api/recruiting/scout/{prospect_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/recruiting/sign/{prospect_id}
`src/dodgeball_sim/server.py` declares `POST /api/recruiting/sign/{prospect_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: POST /api/recruiting/visit/{prospect_id}
`src/dodgeball_sim/server.py` declares `POST /api/recruiting/visit/{prospect_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/roster/release
`src/dodgeball_sim/server.py` declares `POST /api/roster/release` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/saves/build-from-scratch
`src/dodgeball_sim/server.py` declares `POST /api/saves/build-from-scratch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/saves/delete
`src/dodgeball_sim/server.py` declares `POST /api/saves/delete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/saves/load
`src/dodgeball_sim/server.py` declares `POST /api/saves/load` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/saves/new
`src/dodgeball_sim/server.py` declares `POST /api/saves/new` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/saves/unload
`src/dodgeball_sim/server.py` declares `POST /api/saves/unload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sim
`src/dodgeball_sim/server.py` declares `POST /api/sim` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sim/week
`src/dodgeball_sim/server.py` declares `POST /api/sim/week` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/tactics
`src/dodgeball_sim/server.py` declares `POST /api/tactics` 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: frontend/src/components/match-week/command-center/PreSimDashboard.tsx (1404 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/dynasty_cli.py (1986 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/official_engine.py (1425 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/offseason_ceremony.py (1630 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/persistence.py (3902 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/server.py (1590 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dodgeball_sim/use_cases.py (1791 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_dispersed_helpers.py (1922 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/eb6a00c3-427e-48ec-804c-fa43e39ad50a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/eb6a00c3-427e-48ec-804c-fa43e39ad50a/

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.