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

zhaojfifa/worldcup2026

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

202 raw signals (0 security + 202 graph)

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

Complete repo analysis

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

JSON
Combined
62.9
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 181 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 34 Medium 22 Low 108 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 181 Crowd 0 Layer: Software 20 Frontend 1 Security 22 Cicd 1 Quality 70 Api 67
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 62.9/100 with 100.0% coverage. It contains 2069 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 202 findings — concentrated in quality (90), api (67), security (23). Risk profile is high: 2 critical, 34 high, 33 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in scripts/check_auto_llm_factory.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
lines 83
scripts/check_auto_llm_factory.py:83 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/assets/status (frontend/src/api/client.ts:82)
`frontend/src/api/client.ts:82` calls `GET /api/v1/assets/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/assets/status` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/community/heat (frontend/src/api/client.ts:86)
`frontend/src/api/client.ts:86` calls `GET /api/v1/community/heat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/community/heat` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/matches (frontend/src/api/client.ts:68)
`frontend/src/api/client.ts:68` calls `GET /api/v1/matches` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/matches` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/matches/${id} (frontend/src/api/client.ts:69)
`frontend/src/api/client.ts:69` calls `GET /api/v1/matches/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/matches/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/rankings (frontend/src/api/client.ts:88)
`frontend/src/api/client.ts:88` calls `GET /api/v1/rankings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rankings` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/recap/${fixtureId}?lang=${lang} (frontend/src/api/client.ts:71)
`frontend/src/api/client.ts:71` calls `GET /api/v1/recap/${fixtureId}?lang=${lang}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/recap/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/reports/${id} (frontend/src/api/client.ts:70)
`frontend/src/api/client.ts:70` calls `GET /api/v1/reports/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/reports/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/social/channels (frontend/src/api/client.ts:85)
`frontend/src/api/client.ts:85` calls `GET /api/v1/social/channels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/social/channels` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/tokens/wallet/${userId} (frontend/src/api/client.ts:73)
`frontend/src/api/client.ts:73` calls `GET /api/v1/tokens/wallet/${userId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/tokens/wallet/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/users/${userId}/streak (frontend/src/api/client.ts:87)
`frontend/src/api/client.ts:87` calls `GET /api/v1/users/${userId}/streak` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/users/<p>/streak` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/historical_recap_shots.mjs:17)
`scripts/qa/historical_recap_shots.mjs:17` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/intel_rewrite_shots.mjs:30)
`scripts/qa/intel_rewrite_shots.mjs:30` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/lang_interaction_shots.mjs:35)
`scripts/qa/lang_interaction_shots.mjs:35` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/mvp2_evidence_board_shots.mjs:41)
`scripts/qa/mvp2_evidence_board_shots.mjs:41` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/mvp2_locale_consolidation_shots.mjs:47)
`scripts/qa/mvp2_locale_consolidation_shots.mjs:47` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/mvp2_recap_flow_shots.mjs:38)
`scripts/qa/mvp2_recap_flow_shots.mjs:38` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:${PORT}/json/version (scripts/qa/mvp2_scout_pack_shots.mjs:36)
`scripts/qa/mvp2_scout_pack_shots.mjs:36` calls `GET http://localhost:${PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/json/version` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/challenges/${challengeId}/join (frontend/src/api/client.ts:78)
`frontend/src/api/client.ts:78` calls `POST /api/v1/challenges/${challengeId}/join` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/challenges/<p>/join` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/community/subscribe (frontend/src/api/client.ts:79)
`frontend/src/api/client.ts:79` calls `POST /api/v1/community/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/community/subscribe` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/corrections/${matchId}/simulate (frontend/src/api/client.ts:77)
`frontend/src/api/client.ts:77` calls `POST /api/v1/corrections/${matchId}/simulate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/corrections/<p>/simulate` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/events/track (frontend/src/api/client.ts:90)
`frontend/src/api/client.ts:90` calls `POST /api/v1/events/track` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/events/track` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/tokens/checkin (frontend/src/api/client.ts:74)
`frontend/src/api/client.ts:74` calls `POST /api/v1/tokens/checkin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/tokens/checkin` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/tokens/unlock-report (frontend/src/api/client.ts:75)
`frontend/src/api/client.ts:75` calls `POST /api/v1/tokens/unlock-report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/tokens/unlock-report` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `checkin` without auth dependency — backend/app/routers/tokens.py:27
`@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/routers/tokens.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `join_challenge` without auth dependency — backend/app/routers/tokens.py:60
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/tokens.py:60 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `join_intent` without auth dependency — backend/app/routers/growth.py:67
`@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/routers/growth.py:67 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_daily_fixtures` without auth dependency — backend/app/routers/daily_fixtures.py:54
`@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/routers/daily_fixtures.py:54 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_match` without auth dependency — backend/app/routers/matches.py:47
`@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/routers/matches.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `simulate_correction` without auth dependency — backend/app/routers/tokens.py:48
`@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/routers/tokens.py:48 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `subscribe` without auth dependency — backend/app/routers/tokens.py:76
`@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/routers/tokens.py:76 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_click` without auth dependency — backend/app/routers/growth.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/routers/growth.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_event` without auth dependency — backend/app/routers/social.py:33
`@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/routers/social.py:33 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `unlock_report` without auth dependency — backend/app/routers/tokens.py:36
`@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/routers/tokens.py:36 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_daily_fixtures` without auth dependency — backend/app/routers/daily_fixtures.py:47
`@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/routers/daily_fixtures.py:47 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/qa/historical_recap_shots.mjs:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 12 occurrences Frontend route `join` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
12 occurrences
repo-level (12 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in wc-ai-h5.html:512
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
wc-ai-h5.html:512 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/pages/GrowthAdminPage.tsx:45
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/pages/GrowthAdminPage.tsx:45 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/historical_recap_shots.mjs:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/historical_recap_shots.mjs:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/intel_rewrite_shots.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/intel_rewrite_shots.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/lang_interaction_shots.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/lang_interaction_shots.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/mvp2_evidence_board_shots.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/mvp2_evidence_board_shots.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/mvp2_locale_consolidation_shots.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/mvp2_locale_consolidation_shots.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/mvp2_recap_flow_shots.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/mvp2_recap_flow_shots.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/qa/mvp2_scout_pack_shots.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/qa/mvp2_scout_pack_shots.mjs:16 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/app/services/data_sources/api_football.py:65
`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/mvp2_daily_autorun.py:52
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/mvp2_daily_ops.py:249
`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 205 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
1 test file(s) for 222 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `LLM_VERIFY_OUT`, `SHOT_SUFFIX`, `VITE_GROUP_LINK_MY`, `VITE_GROUP_LINK_VI`, `VITE_GROUP_LINK_ZH`. 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 401 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 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/check_daily_content_flow.py:main, scripts/check_llm_grounding.py:main 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.
8 occurrences
repo-level (8 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/check_internal_daily_command_center.py:main, scripts/check_operator_console.py:main, scripts/check_critical_ops_view.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Co…
3 occurrences
repo-level (3 hits)
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 `check_customer_visible_copy` in scripts/check_customer_visible_copy.py:29
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 `check_customer_visible_copy` in scripts/check_fixture_freshness.py:9
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 `check_customer_visible_copy` in scripts/check_homepage_product_loop.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 `check_growth_copy` in scripts/check_growth_copy.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 `check_growth_copy` in scripts/mvp2_editorial_agent.py:45
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 `cta_copy` in frontend/src/pages/EvidenceBoardPage.tsx:63
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 `cta_copy` in frontend/src/pages/RecapDetailPage.tsx:220
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 `free_copy` in scripts/mvp2_generate_rescore_models.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 `generate_copy` in backend/app/routers/llm.py:42
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 `generate_copy` in backend/app/services/llm/copy_service.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 `group_join_copy` in scripts/check_mvp2_product_narrative_guard.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 `has_copy` in scripts/mvp2_daily_ops.py:181
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 `mvp2_evidence_board_v2` in scripts/qa/mvp2_evidence_board_shots.mjs:11
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 `operator_copy` in frontend/src/components/NarrativeView.tsx:42
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 `operator_copy` in frontend/src/components/ProductProofViews.tsx: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 `operator_copy` in scripts/check_mvp2_llm_narrative_guard.py:30
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 `operator_copy` in scripts/mvp2_generate_scoutscore_narrative.py:201
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 `operator_copy` in scripts/mvp2_ops.py:173
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 `operator_recap_copy` in backend/app/routers/internal_scout_pack.py:655
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 `operator_recap_copy` in backend/app/services/scoutscore/accountability.py:212
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 `operator_recap_copy` in backend/app/services/scoutscore/recap_view.py:55
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 `qiuge_v2` in scripts/mvp2_generate_product_proof_narratives.py:183
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 `share_copy` in frontend/src/growth/shareTemplates.ts:63
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 `share_copy` in frontend/src/pages/DailyStatusPage.tsx:101
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 `share_copy` in scripts/check_auto_llm_factory.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 `share_copy` in scripts/check_daily_content_flow.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 `share_copy` in scripts/check_daily_readiness.py:16
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 `share_copy` in scripts/check_llm_copy_attractiveness.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 `share_copy` in scripts/check_llm_copy_quality.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 `share_copy` in scripts/check_prediction_artifact.py:182
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 `share_copy` in scripts/check_recap_generation_flow.py:58
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 `share_copy` in scripts/check_recap_pipeline.py:30
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 `share_copy` in scripts/mvp2_autogen_prediction_draft.py:43
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 `share_copy` in scripts/mvp2_build_daily_prediction_artifact.py:46
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `share_copy` in scripts/mvp2_recommendation_closure.py:104
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 `tientri_v2` in scripts/mvp2_build_rescore_diff.py:179
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 `tientri_v2` in scripts/mvp2_generate_trial_prediction_narratives.py:110
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: asset_exists
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/storage/r2_client.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_build_artifacts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:293
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_build_queue
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:264
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_bundle
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:452
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_close_day
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:336
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_prematch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:188
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_queue
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:497
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_recap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:400
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_recap_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:320
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_review_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:284
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_scan
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:136
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_share_refresh
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:328
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:252
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:522
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_t30_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_daily_ops.py:312
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_watch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_ops.py:324
low System graph software Dead code conf 1.00 Possibly dead Python function: num
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_build_scoutscore_v0_2_factors.py:166
low System graph software Dead code conf 1.00 Possibly dead Python function: rt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/check_llm_grounding.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_lineups
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/jobs/fixtures_sync.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: ts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mvp2_match_sync.py:200
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/lib/freshness.selftest.ts:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /admin/assets/{asset_id}
`backend/app/routers/assets.py` declares `DELETE /admin/assets/{asset_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 /
`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 /admin/dashboard
`backend/app/routers/growth.py` declares `GET /admin/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/export
`backend/app/routers/growth.py` declares `GET /admin/export` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/health
`backend/app/routers/health.py` declares `GET /api/v1/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/health/data-source
`backend/app/routers/health.py` declares `GET /api/v1/health/data-source` 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 /assets/status
`backend/app/routers/assets.py` declares `GET /assets/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 /assets/{asset_id}
`backend/app/routers/assets.py` declares `GET /assets/{asset_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 /community/heat
`backend/app/routers/social.py` declares `GET /community/heat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /daily-fixtures
`backend/app/routers/daily_fixtures.py` declares `GET /daily-fixtures` 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 /data-source/status
`backend/app/routers/data_source.py` declares `GET /data-source/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 /matches
`backend/app/routers/matches.py` declares `GET /matches` 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 /matches/{match_id}
`backend/app/routers/matches.py` declares `GET /matches/{match_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 /performance/daily
`backend/app/routers/performance.py` declares `GET /performance/daily` 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 /performance/summary
`backend/app/routers/performance.py` declares `GET /performance/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 /rankings
`backend/app/routers/rankings.py` declares `GET /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 /recap/{fixture_id}
`backend/app/routers/recap.py` declares `GET /recap/{fixture_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 /reports/{match_id}
`backend/app/routers/matches.py` declares `GET /reports/{match_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 /scout-pack
`backend/app/routers/internal_scout_pack.py` declares `GET /scout-pack` 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 /social/channels
`backend/app/routers/social.py` declares `GET /social/channels` 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 /tokens/wallet/{user_id}
`backend/app/routers/tokens.py` declares `GET /tokens/wallet/{user_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users/{user_id}/streak
`backend/app/routers/rankings.py` declares `GET /users/{user_id}/streak` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /admin/ambassadors/{code}
`backend/app/routers/growth.py` declares `PATCH /admin/ambassadors/{code}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/ambassadors
`backend/app/routers/growth.py` declares `POST /admin/ambassadors` 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 /admin/assets/upload
`backend/app/routers/assets.py` declares `POST /admin/assets/upload` 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 /admin/challenges/settle
`backend/app/routers/rankings.py` declares `POST /admin/challenges/settle` 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 /admin/contributions
`backend/app/routers/growth.py` declares `POST /admin/contributions` 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 /admin/contributions/{contribution_id}/review
`backend/app/routers/growth.py` declares `POST /admin/contributions/{contribution_id}/review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/daily-fixtures/refresh
`backend/app/routers/daily_fixtures.py` declares `POST /admin/daily-fixtures/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/daily-fixtures/upload
`backend/app/routers/daily_fixtures.py` declares `POST /admin/daily-fixtures/upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/intents/{intent_id}/confirm
`backend/app/routers/growth.py` declares `POST /admin/intents/{intent_id}/confirm` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/social/channels/upsert
`backend/app/routers/social.py` declares `POST /admin/social/channels/upsert` 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 /challenges/{challenge_id}/join
`backend/app/routers/tokens.py` declares `POST /challenges/{challenge_id}/join` 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 /click
`backend/app/routers/growth.py` declares `POST /click` 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 /community/subscribe
`backend/app/routers/tokens.py` declares `POST /community/subscribe` 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 /corrections/{match_id}/simulate
`backend/app/routers/tokens.py` declares `POST /corrections/{match_id}/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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /events/track
`backend/app/routers/social.py` declares `POST /events/track` 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 /generate-copy
`backend/app/routers/llm.py` declares `POST /generate-copy` 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 /join-intent
`backend/app/routers/growth.py` declares `POST /join-intent` 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 /matches/{match_id}/refresh
`backend/app/routers/matches.py` declares `POST /matches/{match_id}/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sync/fixtures
`backend/app/routers/admin.py` declares `POST /sync/fixtures` 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 /sync/results
`backend/app/routers/admin.py` declares `POST /sync/results` 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 /tokens/checkin
`backend/app/routers/tokens.py` declares `POST /tokens/checkin` 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 /tokens/unlock-report
`backend/app/routers/tokens.py` declares `POST /tokens/unlock-report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
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/fd2a7cac-418e-498d-949a-55aef7516a75/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/fd2a7cac-418e-498d-949a-55aef7516a75/

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.