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

twonezerotwo-hue/e-yay-codex

https://github.com/twonezerotwo-hue/e-yay-codex · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

227 raw signals (0 security + 227 graph)

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

Complete repo analysis

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

JSON
Combined
66.8
/100
Security checks
67
0 findings
System graph
67
100.0% cov · 216 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 39 Medium 12 Low 136 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 216 Crowd 0 Layer: Software 5 Frontend 21 Hardware 3 Security 14 Cicd 1 Quality 96 Api 76
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 66.8/100 with 100.0% coverage. It contains 4482 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 227 findings — concentrated in quality (106), api (76), frontend (21). Risk profile is high: 0 critical, 39 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 187 of 216 actionable findings. 227 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 api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/banner (frontend/components/AgentCommandCenter.tsx:347)
`frontend/components/AgentCommandCenter.tsx:347` calls `GET /api/backend/agent/banner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/banner` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/banner (frontend/components/AgentInsightBar.tsx:131)
`frontend/components/AgentInsightBar.tsx:131` calls `GET /api/backend/agent/banner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/banner` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/banner (frontend/components/AgentMainPanel.tsx:237)
`frontend/components/AgentMainPanel.tsx:237` calls `GET /api/backend/agent/banner` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/banner` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/chart/${signal.asset_code}?timeframes=1h,4h,1d (frontend/components/AssetGrid.tsx:323)
`frontend/components/AssetGrid.tsx:323` calls `GET /api/backend/agent/chart/${signal.asset_code}?timeframes=1h,4h,1d` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/chart/<p>` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/insight (frontend/components/AgentCommandCenter.tsx:380)
`frontend/components/AgentCommandCenter.tsx:380` calls `GET /api/backend/agent/insight` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/insight` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/insight (frontend/components/AgentInsightBar.tsx:153)
`frontend/components/AgentInsightBar.tsx:153` calls `GET /api/backend/agent/insight` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/insight` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/agent/trade-opinion (frontend/components/AgentCommandCenter.tsx:363)
`frontend/components/AgentCommandCenter.tsx:363` calls `GET /api/backend/agent/trade-opinion` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/agent/trade-opinion` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/alerts/recent?limit=1 (frontend/components/PaperTradingTicker.tsx:422)
`frontend/components/PaperTradingTicker.tsx:422` calls `GET /api/backend/alerts/recent?limit=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/alerts/recent` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/alerts/recent?limit=20 (frontend/components/PaperTradingTicker.tsx:400)
`frontend/components/PaperTradingTicker.tsx:400` calls `GET /api/backend/alerts/recent?limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/alerts/recent` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/breaking-news/visual (frontend/components/BreakingNewsRadarLayer.tsx:223)
`frontend/components/BreakingNewsRadarLayer.tsx:223` calls `GET /api/backend/breaking-news/visual` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/breaking-news/visual` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/capital-rotation/visual (frontend/components/CapitalFlowAnimatedLayer.tsx:224)
`frontend/components/CapitalFlowAnimatedLayer.tsx:224` calls `GET /api/backend/capital-rotation/visual` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/capital-rotation/visual` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/chart-patterns (frontend/components/PaperTradingTicker.tsx:390)
`frontend/components/PaperTradingTicker.tsx:390` calls `GET /api/backend/chart-patterns` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/chart-patterns` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/learning/summary (frontend/components/LearningPanel.tsx:385)
`frontend/components/LearningPanel.tsx:385` calls `GET /api/backend/learning/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/learning/summary` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/system-health/summary (frontend/components/SystemHealthPanel.tsx:160)
`frontend/components/SystemHealthPanel.tsx:160` calls `GET /api/backend/system-health/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/system-health/summary` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/trading/state (frontend/components/AgentCommandCenter.tsx:381)
`frontend/components/AgentCommandCenter.tsx:381` calls `GET /api/backend/trading/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/trading/state (frontend/components/AgentMainPanel.tsx:166)
`frontend/components/AgentMainPanel.tsx:166` calls `GET /api/backend/trading/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/trading/state (frontend/components/PaperTradingTicker.tsx:326)
`frontend/components/PaperTradingTicker.tsx:326` calls `GET /api/backend/trading/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/trading/state (frontend/components/PaperTradingTicker.tsx:461)
`frontend/components/PaperTradingTicker.tsx:461` calls `GET /api/backend/trading/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/backend/trading/state (frontend/components/PaperTradingTicker.tsx:761)
`frontend/components/PaperTradingTicker.tsx:761` calls `GET /api/backend/trading/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/close/${pair} (frontend/components/PaperTradingTicker.tsx:460)
`frontend/components/PaperTradingTicker.tsx:460` calls `POST /api/backend/trading/close/${pair}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/close/<p>` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/manual-ready/${pair}/dismiss (frontend/components/PaperTradingTicker.tsx:584)
`frontend/components/PaperTradingTicker.tsx:584` calls `POST /api/backend/trading/manual-ready/${pair}/dismiss` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/manual-ready/<p>/dismiss` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/manual-ready/${pair}/open (frontend/components/PaperTradingTicker.tsx:572)
`frontend/components/PaperTradingTicker.tsx:572` calls `POST /api/backend/trading/manual-ready/${pair}/open` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/manual-ready/<p>/open` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/pending/${pair}/reject (frontend/components/PaperTradingTicker.tsx:560)
`frontend/components/PaperTradingTicker.tsx:560` calls `POST /api/backend/trading/pending/${pair}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/pending/<p>/reject` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/signal-chain/${asset}/cancel (frontend/components/AgentMainPanel.tsx:211)
`frontend/components/AgentMainPanel.tsx:211` calls `POST /api/backend/trading/signal-chain/${asset}/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/signal-chain/<p>/cancel` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/state/repair (frontend/components/PaperTradingTicker.tsx:520)
`frontend/components/PaperTradingTicker.tsx:520` calls `POST /api/backend/trading/state/repair` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state/repair` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/backend/trading/state/reset (frontend/components/PaperTradingTicker.tsx:501)
`frontend/components/PaperTradingTicker.tsx:501` calls `POST /api/backend/trading/state/reset` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/backend/trading/state/reset` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — backend/app/api/chat.py:42
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/chat.py:42 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `critique_payload` without auth dependency — backend/app/api/agent_critique.py:157
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/agent_critique.py:157 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `forget` without auth dependency — backend/app/api/agent_memory.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/api/agent_memory.py:76 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `invoke_tool` without auth dependency — backend/app/api/agent_tools.py:34
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/agent_tools.py:34 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `market_strategist_chat` without auth dependency — backend/app/api/market_strategist.py:45
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/market_strategist.py:45 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_owner_feedback` without auth dependency — backend/app/api/learning.py:61
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/learning.py:61 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_rebalance_approve` without auth dependency — backend/app/api/learning.py:108
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/learning.py:108 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_rebalance_propose` without auth dependency — backend/app/api/learning.py:89
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/learning.py:89 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `remember` without auth dependency — backend/app/api/agent_memory.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/api/agent_memory.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_ensemble` without auth dependency — backend/app/api/agent_ensemble.py:150
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/agent_ensemble.py:150 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_eval` without auth dependency — backend/app/api/agent_eval.py:28
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/agent_eval.py:28 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_ai_report_job` without auth dependency — backend/app/api/ai_report.py:312
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/ai_report.py:312 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_ensemble_job` without auth dependency — backend/app/api/agent_ensemble.py:162
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/agent_ensemble.py:162 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/AssetGrid.tsx:323
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/BreakingNewsRadarLayer.tsx:223
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/CapitalFlowAnimatedLayer.tsx:224
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/PaperTradingTicker.tsx:326
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/lib/api.ts:8
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/update_event_calendar.py:389
`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/verify_and_snapshot.py:54
`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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 58 placeholder/mock markers across 21 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 19 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 21, 50
.github/workflows/ci.yml:21, 50 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/components/PaperTradingTicker.tsx:1200
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: backend/app/api/agent_stream.py:gen, backend/app/api/agent_stream.py:gen 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: backend/app/market_state/risk_gate_view.py:to_dict, backend/app/market_state/risk_gate_view.py:to_dict, backend/app/market_state/risk_gate_view.py:to_dict This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.h…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 59 places
Functions with the same first-5-line body hash: backend/app/services/snapshot_replay_source_diagnostics.py:build_source_freshness_decay_timeline, backend/app/services/snapshot_replay_source_diagnostics.py:build_fallback_usage_recurrence, backend/app/services/snapshot_replay_source_diagnostics.py:bu…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 65 places
Functions with the same first-5-line body hash: backend/app/api/snapshot_replay_routes_source_quality.py:snapshot_backtest_source_gap_recurrence_leaderboard, backend/app/api/snapshot_replay_routes_source_quality.py:snapshot_backtest_raw_payload_reference_completeness, backend/app/api/snapshot_repla…
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 `agent_hourly_thesis_v1` in backend/app/services/agent_hourly_thesis_service.py:28
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 `agent_hourly_thesis_v1` in backend/app/storage/agent_thesis_store.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 `agent_hourly_thesis_v1` in backend/tests/test_agent_thesis_sanity.py:21
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 `ai_trade_opinion_v1` in backend/app/services/ai_trade_opinion_service.py:14
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 `ai_trade_opinion_v1` in backend/app/storage/ai_trade_opinion_store.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 `ai_trade_opinion_v1` in frontend/components/AgentCommandCenter.tsx:83
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 `auto_backup` in backend/app/services/position_management_service.py:561
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 `auto_plan_backup` in backend/app/services/paper_trading_service.py:392
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 `auto_plan_backup` in frontend/components/PaperTradingTicker.tsx:76
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 `auto_tune_adjustment_v1` in backend/app/storage/auto_tune_store.py:41
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 `auto_tune_overrides_v1` in backend/tests/test_auto_tune_override_reader.py:50
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 `breaking_news_visual_v1` in backend/app/services/breaking_news_visual_adapter.py:14
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 `capital_rotation_visual_v1` in backend/app/api/capital_rotation_visual.py:48
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 `capital_rotation_visual_v1` in backend/app/services/capital_rotation_visual_adapter.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 `closes_old` in backend/tests/test_sr_quality_service.py:97
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 `create_clean_backup` in scripts/verify_and_snapshot.py:216
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 `existing_backup` in tests/test_verify_and_snapshot.py:123
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 `feature_registry_v1` in reports/generator.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 `feature_registry_v1` in tests/test_phase1_config.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 `hourly_snapshot_v1` in backend/app/api/hourly_snapshots.py:34
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 `hourly_snapshot_v1` in backend/app/storage/hourly_snapshot_store.py:24
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 `hourly_snapshot_v1` in backend/tests/test_agent_hourly_thesis_service.py:48
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 `hourly_snapshot_v1` in backend/tests/test_hourly_snapshots_api.py:112
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `learning_candidate_v1` in backend/app/services/learning_candidate_service.py:5
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 `learning_candidate_v1` in backend/app/storage/learning_candidate_store.py:31
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 `learning_candidate_v1` in backend/tests/test_learning_candidate.py:588
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 `learning_candidate_v1` in backend/tests/test_mistake_memory.py:127
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 `mistake_memory_v1` in backend/app/services/mistake_memory_service.py:41
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 `mistake_memory_v1` in backend/app/storage/mistake_memory_store.py:34
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 `mistake_memory_v1` in backend/tests/test_weekly_calibration.py:41
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 `position_recheck_v1` in backend/app/services/position_recheck_service.py:33
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 `position_recheck_v1` in backend/app/storage/position_recheck_store.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 `position_recheck_v1` in backend/tests/test_position_recheck.py:376
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 `safe_old` in backend/tests/test_agent_thesis_context.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 `scheduler_run_v1` in backend/app/storage/scheduler_run_store.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 `source_registry_v1` in backend/app/dashboard/gradio_dashboard.py:401
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 `source_registry_v1` in backend/app/providers/stooq_adapter.py:144
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 `source_registry_v1` in registry/source_registry.py:51
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 `source_registry_v1` in tests/test_source_registry.py:21
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_manual_sl_tp_saves_auto_plan_backup` in backend/tests/test_position_management.py:272
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_report_surfaces_stale_source_diagnostics_when_observations_are_old` in tests/test_phase1_report_audit.py:77
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_schema_version_is_hourly_snapshot_v1` in backend/tests/test_hourly_snapshot_store.py:178
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 `verified_provider_adapter_v1` in backend/app/services/snapshot_replay_source_common.py:151
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 `verified_provider_adapter_v1` in backend/app/services/source_observation_service.py:77
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 `verified_provider_adapter_v1` in backend/tests/test_ceo_report_api.py:62
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 `verified_provider_adapter_v1` in backend/tests/test_provider_ingestion_service.py:75
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 `verified_provider_adapter_v1` in backend/tests/test_snapshot_replay_api.py:81
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 `verified_provider_adapter_v1` in backend/tests/test_snapshot_replay_service.py:113
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 `verified_provider_adapter_v1` in backend/tests/test_source_observation_service.py:72
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 `verified_provider_adapter_v1` in backend/tests/test_stooq_ingestion.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 `weekly_calibration_v1` in backend/app/services/weekly_calibration_service.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 `weekly_calibration_v1` in backend/app/storage/weekly_calibration_store.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 `weekly_calibration_v1` in backend/tests/test_auto_tune.py:59
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 `weekly_calibration_v1` in backend/tests/test_learning_summary.py:54
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: build_source_freshness_decay_timeline
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/snapshot_replay_source_diagnostics.py:84
low System graph software Dead code conf 1.00 Possibly dead Python function: calculate_from_snapshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/data_quality_service.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: run_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/verify_and_snapshot.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/versions/20260518_0001_create_audit_logs.py:20
low System graph software Dead code conf 1.00 Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/versions/20260519_0002_create_market_snapshots.py:20
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/lib/__tests__/formatPrice.verify.ts:12
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 quality Integrity conf 1.00 Stub function `add` (body is just `pass`/`return`) — backend/app/dashboard/gradio_dashboard.py:422
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/app/api/chart_patterns.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 /active-weights
`backend/app/api/learning.py` declares `GET /active-weights` 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 /anthropic
`backend/app/api/agent_tools.py` declares `GET /anthropic` 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 /backtest/raw-payload-reference-completeness
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/raw-payload-reference-completeness` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-decision-usage-consistency
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-decision-usage-consistency` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-average-coverage-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-average-coverage-drift` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-critical-feature-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-critical-feature-drift` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-high-severity-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-high-severity-drift` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-info-feature-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-info-feature-drift` 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 — consid…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-minimum-coverage-floor-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-minimum-coverage-floor-reconciliation` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-missing-asset-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-missing-asset-count-reconciliation` 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 de…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-missing-source-feature-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-missing-source-feature-count-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwis…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-ready-feature-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-ready-feature-drift` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-label-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-label-drift` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-rank-density-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-rank-density-drift` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-rank-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-rank-drift` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-rank-spread-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-rank-spread-drift` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-critical-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-critical-count-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Other…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-feature-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-feature-count-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherw…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-info-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-info-count-reconciliation` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-non-actionable-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-non-actionable-count-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks).…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-rank-gap-continuity-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-rank-gap-continuity-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-rank-gap-magnitude-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-rank-gap-magnitude-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). O…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-rank-label-consistency-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-rank-label-consistency-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-rank-order-continuity-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-rank-order-continuity-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks)…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-severity-ranking-warning-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-severity-ranking-warning-count-reconciliation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherw…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-stale-asset-count-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-stale-asset-count-reconciliation` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-stale-feature-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-stale-feature-drift` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-warning-feature-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-warning-feature-drift` 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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-diagnostics-zero-rank-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-diagnostics-zero-rank-drift` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-gap-recurrence-leaderboard
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-gap-recurrence-leaderboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-observation-confidence-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-observation-confidence-drift` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-observation-record-summary-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-observation-record-summary-reconciliation` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-observation-summary-drift
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-observation-summary-drift` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/source-record-completeness
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/source-record-completeness` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backtest/verified-source-coverage-reconciliation
`backend/app/api/snapshot_replay_routes_source_quality.py` declares `GET /backtest/verified-source-coverage-reconciliation` 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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /current
`backend/app/api/ai_report.py` declares `GET /current` 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-report
`backend/app/api/learning.py` declares `GET /daily-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
low System graph api Wiring conf 1.00 Unused endpoint: GET /insight
`backend/app/api/agent_insight.py` declares `GET /insight` 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 /jobs
`backend/app/api/ai_report.py` declares `GET /jobs` 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 /jobs/{job_id}
`backend/app/api/ai_report.py` declares `GET /jobs/{job_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 /owner-feedback/recent
`backend/app/api/learning.py` declares `GET /owner-feedback/recent` 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 /rebalance/proposals
`backend/app/api/learning.py` declares `GET /rebalance/proposals` 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 /summary
`backend/app/api/system_health.py` declares `GET /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 /{pair}
`backend/app/api/chart_patterns.py` declares `GET /{pair}` 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 /invoke
`backend/app/api/agent_tools.py` declares `POST /invoke` 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 /jobs
`backend/app/api/ai_report.py` declares `POST /jobs` 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 /owner-feedback
`backend/app/api/learning.py` declares `POST /owner-feedback` 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 /rebalance/approve
`backend/app/api/learning.py` declares `POST /rebalance/approve` 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 /rebalance/propose
`backend/app/api/learning.py` declares `POST /rebalance/propose` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/app/api/snapshot_replay_routes_source_quality.py (1283 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/api/snapshot_replay_source_serializers_registry.py (1266 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/paper_trading_service.py (3099 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/regime_report_service.py (2348 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/snapshot_replay_source_quality_drift_summary.py (1175 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/snapshot_replay_source_quality_reconciliation_counts_severity.py (1220 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/snapshot_replay_source_quality_reconciliation_order.py (1038 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/snapshot_replay_source_registry_verification.py (1279 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/test_snapshot_replay_api.py (5236 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/test_snapshot_replay_service.py (8435 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/AgentCommandCenter.tsx (1205 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/AgentHolographicLayer.tsx (1316 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/PaperTradingTicker.tsx (2438 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/91a51223-2578-484e-bacb-8e28b80f15d9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/91a51223-2578-484e-bacb-8e28b80f15d9/

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.