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

RevanParimi/StockAgent

https://github.com/RevanParimi/StockAgent · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

204 raw signals (0 security + 204 graph)

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

Complete repo analysis

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

JSON
Combined
51.8
/100
Security checks
52
0 findings
System graph
52
100.0% cov · 184 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 61 Medium 15 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 184 Crowd 0 Layer: Software 18 Frontend 1 Hardware 6 Security 21 Cicd 1 Quality 52 Api 85
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 51.8/100 with 100.0% coverage. It contains 4625 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 204 findings — concentrated in api (85), quality (72), security (21). Risk profile is high: 0 critical, 61 high, 18 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 168 of 184 actionable findings. 204 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: DELETE /ui/tickers/managed/${sym} (src/frontend/prototypes/logs.jsx:246)
`src/frontend/prototypes/logs.jsx:246` calls `DELETE /ui/tickers/managed/${sym}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/tickers/managed/<p>` 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 /analytics/agent-accuracy (src/frontend/prototypes/analytics.jsx:278)
`src/frontend/prototypes/analytics.jsx:278` calls `GET /analytics/agent-accuracy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/agent-accuracy` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /analytics/conviction-outcomes (src/frontend/prototypes/analytics.jsx:281)
`src/frontend/prototypes/analytics.jsx:281` calls `GET /analytics/conviction-outcomes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/conviction-outcomes` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /analytics/miss-breakdown (src/frontend/prototypes/analytics.jsx:280)
`src/frontend/prototypes/analytics.jsx:280` calls `GET /analytics/miss-breakdown` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/miss-breakdown` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /analytics/sector-comparison (src/frontend/prototypes/analytics.jsx:282)
`src/frontend/prototypes/analytics.jsx:282` calls `GET /analytics/sector-comparison` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/sector-comparison` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /analytics/weight-drift (src/frontend/prototypes/analytics.jsx:279)
`src/frontend/prototypes/analytics.jsx:279` calls `GET /analytics/weight-drift` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/weight-drift` 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 /ui/agents?sector=${sector} (src/frontend/prototypes/agents-page.jsx:25)
`src/frontend/prototypes/agents-page.jsx:25` calls `GET /ui/agents?sector=${sector}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/agents` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/bootstrap (src/frontend/prototypes/data.jsx:641)
`src/frontend/prototypes/data.jsx:641` calls `GET /ui/bootstrap` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/bootstrap` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/bootstrap (src/frontend/web/src/stores/sectorStore.ts:34)
`src/frontend/web/src/stores/sectorStore.ts:34` calls `GET /ui/bootstrap` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/bootstrap` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/learnings (src/frontend/prototypes/data.jsx:679)
`src/frontend/prototypes/data.jsx:679` calls `GET /ui/learnings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/learnings` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/nifty-ranges?range=${newRange} (src/frontend/prototypes/home.jsx:444)
`src/frontend/prototypes/home.jsx:444` calls `GET /ui/nifty-ranges?range=${newRange}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/nifty-ranges` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/prompts/${sector}/${agent} (src/frontend/prototypes/prompt-lab.jsx:203)
`src/frontend/prototypes/prompt-lab.jsx:203` calls `GET /ui/prompts/${sector}/${agent}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/prompts/<p>/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/prompts/catalogue (src/frontend/prototypes/prompt-lab.jsx:184)
`src/frontend/prototypes/prompt-lab.jsx:184` calls `GET /ui/prompts/catalogue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/prompts/catalogue` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/prompts/status (src/frontend/prototypes/prompt-lab.jsx:177)
`src/frontend/prototypes/prompt-lab.jsx:177` calls `GET /ui/prompts/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/prompts/status` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/rl/misses/${ticker} (src/frontend/prototypes/rl-data.jsx:202)
`src/frontend/prototypes/rl-data.jsx:202` calls `GET /ui/rl/misses/${ticker}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/rl/misses/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/rl/predictions/${ticker} (src/frontend/prototypes/rl-data.jsx:200)
`src/frontend/prototypes/rl-data.jsx:200` calls `GET /ui/rl/predictions/${ticker}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/rl/predictions/<p>` 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 /ui/rl/summary/${ticker} (src/frontend/prototypes/rl-data.jsx:199)
`src/frontend/prototypes/rl-data.jsx:199` calls `GET /ui/rl/summary/${ticker}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/rl/summary/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/rl/tickers (src/frontend/prototypes/rl-data.jsx:182)
`src/frontend/prototypes/rl-data.jsx:182` calls `GET /ui/rl/tickers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/rl/tickers` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/rl/weights/${ticker} (src/frontend/prototypes/rl-data.jsx:201)
`src/frontend/prototypes/rl-data.jsx:201` calls `GET /ui/rl/weights/${ticker}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/rl/weights/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/search?q=${encodeURIComponent(val)} (src/frontend/prototypes/home.jsx:147)
`src/frontend/prototypes/home.jsx:147` calls `GET /ui/search?q=${encodeURIComponent(val)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/search` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/tickers/managed (src/frontend/prototypes/analytics.jsx:283)
`src/frontend/prototypes/analytics.jsx:283` calls `GET /ui/tickers/managed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/tickers/managed` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/tickers/managed (src/frontend/prototypes/logs.jsx:228)
`src/frontend/prototypes/logs.jsx:228` calls `GET /ui/tickers/managed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/tickers/managed` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/trending (src/frontend/prototypes/home.jsx:715)
`src/frontend/prototypes/home.jsx:715` calls `GET /ui/trending` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/trending` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/trending (src/frontend/web/src/stores/sectorStore.ts:50)
`src/frontend/web/src/stores/sectorStore.ts:50` calls `GET /ui/trending` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/trending` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/watchlist (src/frontend/prototypes/home.jsx:570)
`src/frontend/prototypes/home.jsx:570` calls `GET /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/watchlist (src/frontend/prototypes/home.jsx:601)
`src/frontend/prototypes/home.jsx:601` calls `GET /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/watchlist (src/frontend/prototypes/home.jsx:619)
`src/frontend/prototypes/home.jsx:619` calls `GET /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /ui/watchlist (src/frontend/web/src/stores/watchlistStore.ts:24)
`src/frontend/web/src/stores/watchlistStore.ts:24` calls `GET /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /ui/tickers/managed/${sym}/toggle (src/frontend/prototypes/logs.jsx:240)
`src/frontend/prototypes/logs.jsx:240` calls `PATCH /ui/tickers/managed/${sym}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/tickers/managed/<p>/toggle` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ui/chat (src/frontend/prototypes/sphere.jsx:287)
`src/frontend/prototypes/sphere.jsx:287` calls `POST /ui/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/chat` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ui/chat (src/frontend/web/src/features/chatbot/useChatHistory.ts:39)
`src/frontend/web/src/features/chatbot/useChatHistory.ts:39` calls `POST /ui/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/chat` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ui/chat/stream (src/frontend/prototypes/sphere.jsx:223)
`src/frontend/prototypes/sphere.jsx:223` calls `POST /ui/chat/stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/chat/stream` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ui/prompts/deploy (src/frontend/prototypes/prompt-lab.jsx:257)
`src/frontend/prototypes/prompt-lab.jsx:257` calls `POST /ui/prompts/deploy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/prompts/deploy` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /ui/tickers/managed/${sym} (src/frontend/prototypes/logs.jsx:255)
`src/frontend/prototypes/logs.jsx:255` calls `POST /ui/tickers/managed/${sym}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/tickers/managed/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/agents/tasks (src/frontend/prototypes/agents-page.jsx:105)
`src/frontend/prototypes/agents-page.jsx:105` calls `PUT /ui/agents/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/agents/tasks` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/agents/weights?sector=${activeSector} (src/frontend/prototypes/agents-page.jsx:47)
`src/frontend/prototypes/agents-page.jsx:47` calls `PUT /ui/agents/weights?sector=${activeSector}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/agents/weights` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/categories/${cat.key}/tickers (src/frontend/prototypes/home.jsx:1379)
`src/frontend/prototypes/home.jsx:1379` calls `PUT /ui/categories/${cat.key}/tickers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/categories/<p>/tickers` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/prompts/${sector}/${agent} (src/frontend/prototypes/prompt-lab.jsx:229)
`src/frontend/prototypes/prompt-lab.jsx:229` calls `PUT /ui/prompts/${sector}/${agent}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/prompts/<p>/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/watchlist (src/frontend/prototypes/home.jsx:590)
`src/frontend/prototypes/home.jsx:590` calls `PUT /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/watchlist (src/frontend/prototypes/home.jsx:612)
`src/frontend/prototypes/home.jsx:612` calls `PUT /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/watchlist (src/frontend/web/src/stores/watchlistStore.ts:36)
`src/frontend/web/src/stores/watchlistStore.ts:36` calls `PUT /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /ui/watchlist (src/frontend/web/src/stores/watchlistStore.ts:49)
`src/frontend/web/src/stores/watchlistStore.ts:49` calls `PUT /ui/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ui/watchlist` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `remove_managed_ticker` without auth dependency — services/api/routes/ui_data.py:3492
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3492 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `toggle_managed_ticker` without auth dependency — services/api/routes/ui_data.py:3519
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3519 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_managed_ticker` without auth dependency — services/api/routes/ui_data.py:3385
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3385 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyse` without auth dependency — services/api/routes/analyse.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.
services/api/routes/analyse.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `chat_stream` without auth dependency — services/api/routes/ui_data.py:3133
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3133 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — services/api/routes/ui_data.py:2846
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:2846 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `deploy_prompts` without auth dependency — services/api/routes/prompts.py:562
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/prompts.py:562 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_backfill` without auth dependency — services/api/routes/scheduler_api.py:260
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/scheduler_api.py:260 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_daily_review` without auth dependency — services/api/routes/scheduler_api.py:205
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/scheduler_api.py:205 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_envelope_generation` without auth dependency — services/api/routes/ui_data.py:3480
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3480 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_forecast` without auth dependency — services/api/routes/scheduler_api.py:169
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/scheduler_api.py:169 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_prompt` without auth dependency — services/api/routes/prompts.py:512
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/prompts.py:512 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `replace_managed_tickers` without auth dependency — services/api/routes/ui_data.py:3333
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:3333 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_agent_tasks` without auth dependency — services/api/routes/ui_data.py:1007
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:1007 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_agent_weights` without auth dependency — services/api/routes/ui_data.py:653
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:653 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_category_tickers` without auth dependency — services/api/routes/ui_data.py:1090
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:1090 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_watchlist` without auth dependency — services/api/routes/ui_data.py:1042
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/api/routes/ui_data.py:1042 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in core/intelligence/rl/algorithms/factor_regime.py:75
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
core/intelligence/rl/algorithms/factor_regime.py:75 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in scripts/api_exploration/iima_ff_factors.py:47
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
scripts/api_exploration/iima_ff_factors.py:47 Tls verify false
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/frontend/prototypes/sphere.jsx:347
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/frontend/prototypes/logs.jsx:240
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 — src/frontend/prototypes/rl-data.jsx:202
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 — src/frontend/prototypes/sw.js:72
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: services/csharp/StockAgent.Scheduler/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 4 occurrences Frontend route `/agents` has no Link/navigate to it — src/frontend/web/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.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/api/server.py:329
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/api/server.py:329 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/frontend/prototypes/sphere.jsx:347
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/frontend/prototypes/sphere.jsx:347 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — new-product.py:530
`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/api_exploration/fyers_explorer.py:95
`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 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 30 placeholder/mock markers across 15 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph 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 325 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: mcr.microsoft.com/dotnet/aspnet:8.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
services/csharp/StockAgent.Scheduler/Dockerfile:16 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/sdk:8.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
services/csharp/StockAgent.Scheduler/Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:6 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
144 tests / 756 src (ratio 0.19).
low System graph quality Integrity conf 1.00 11 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: services/api/routes/prompts.py:get_prompt, services/api/routes/prompts.py:put_prompt 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.
11 occurrences
repo-level (11 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 20 places
Functions with the same first-5-line body hash: core/sectors/realestate/fundamentals.py:agent_name, core/sectors/logistics/fundamentals.py:agent_name, core/sectors/media/fundamentals.py:agent_name, core/sectors/tech/fundamentals.py:agent_name This is *the* AI-coder failure mode (4× more duplicatio…
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/backend/sectors/banking_bfsi/agents/fundamentals.py:agent_name, src/backend/sectors/renewable_energy/agents/fundamentals.py:agent_name, src/backend/sectors/it_sector/agents/fundamentals.py:agent_name This is *the* AI-coder failure mode (4× more d…
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 `06_v1` in tests/unit/intelligence/rl/test_reforecast_cli.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 `broken_by_old` in tests/test_weight_init_fix.py:214
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 `days_old` in core/intelligence/rl/workflows/generate_forecast.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 `model_copy` in core/intelligence/rl/agents/dossier_curator.py:187
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 `model_copy` in core/intelligence/rl/workflows/daily_review.py:873
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 `model_copy` in src/backend/shared/pipeline/graphs/rails.py:99
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 `model_copy` in tests/unit/intelligence/rl/eval/test_scorecard.py:250
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 `model_copy` in tests/unit/intelligence/rl/test_lesson_emphasis.py:47
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 `model_copy` in tests/unit/intelligence/rl/test_matching_lessons.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 `model_copy` in tests/unit/intelligence/rl/test_scorecard_schemas.py:139
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_archive_envelope_creates_v1` in tests/unit/intelligence/rl/test_envelope_archive.py:36
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_enhancer_v2` in tests/unit/intelligence/rl/test_enhancer_v2.py:2
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_flag_on_empty_outputs_with_fallback_enabled_runs_legacy` in tests/unit/test_orchestrator_unified_branch.py:122
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_resurrect_confidence_floor_from_old` in tests/unit/intelligence/rl/test_forgetting.py:429
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_system_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/config/prompts/shared/feedback_agent.py:24
low System graph software Dead code conf 1.00 Possibly dead Python function: build_system_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/prompts/feedback_agent.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: conflict_rail
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/pipeline/graphs/rails.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: earningsapi_get_transcript
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/api_exploration/earnings_api_explorer.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: emit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/api/log_buffer.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: exchange_code
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/api_exploration/fyers_explorer.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_option_chain
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/intelligence/fno/fetcher.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: find_schemes_holding_stock
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/api_exploration/amfi_mf_explorer.py:81
low System graph software Dead code conf 1.00 Possibly dead Python function: format_feedback_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/config/prompts/shared/feedback_agent.py:212
low System graph software Dead code conf 1.00 Possibly dead Python function: format_feedback_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/prompts/feedback_agent.py:188
low System graph software Dead code conf 1.00 Possibly dead Python function: formatTime
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/api/server.py:56
low System graph software Dead code conf 1.00 Possibly dead Python function: lifetime_hit_rate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/schemas/feedback.py:398
low System graph software Dead code conf 1.00 Possibly dead Python function: load_validation_state
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/intelligence/seasonal/validator.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: output_rail
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/pipeline/graphs/rails.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: remaining_forecasts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/backend/shared/schemas/feedback.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: run_now
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/scheduler/python/scheduler.py:686
low System graph software Dead code conf 1.00 Possibly dead Python function: show_preopen_movers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/api_exploration/nse_insider_scraper.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: trading_dates
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/intelligence/rl/nse_calendar.py:149
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 api Wiring conf 1.00 Unused endpoint: DELETE /tickers/managed/{sym}
`services/api/routes/ui_data.py` declares `DELETE /tickers/managed/{sym}` 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 /agent-accuracy
`services/api/routes/analytics.py` declares `GET /agent-accuracy` 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 /agents
`services/api/routes/ui_data.py` declares `GET /agents` 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 /agents/tasks
`services/api/routes/ui_data.py` declares `GET /agents/tasks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /bootstrap
`services/api/routes/ui_data.py` declares `GET /bootstrap` 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 /catalogue
`services/api/routes/prompts.py` declares `GET /catalogue` 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 /categories
`services/api/routes/ui_data.py` declares `GET /categories` 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 /conviction-outcomes
`services/api/routes/analytics.py` declares `GET /conviction-outcomes` 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 /history/{ticker}/latest
`services/api/routes/history.py` declares `GET /history/{ticker}/latest` 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 /learnings
`services/api/routes/ui_data.py` declares `GET /learnings` 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 /logs
`services/api/routes/ui_data.py` declares `GET /logs` 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 /logs/stream
`services/api/routes/ui_data.py` declares `GET /logs/stream` 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 /market/summary
`services/api/routes/ui_data.py` declares `GET /market/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 /miss-breakdown
`services/api/routes/analytics.py` declares `GET /miss-breakdown` 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 /nifty-ranges
`services/api/routes/ui_data.py` declares `GET /nifty-ranges` 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 /pending
`services/api/routes/prompts.py` declares `GET /pending` 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 /powerbi-feed
`services/api/routes/analytics.py` declares `GET /powerbi-feed` 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 /powerbi-feed/$metadata
`services/api/routes/analytics.py` declares `GET /powerbi-feed/$metadata` 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 /rl-export
`services/api/routes/analytics.py` declares `GET /rl-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 /search
`services/api/routes/ui_data.py` declares `GET /search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sector-comparison
`services/api/routes/analytics.py` declares `GET /sector-comparison` 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 /tickers
`services/api/server.py` declares `GET /tickers` 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 /tickers/managed
`services/api/routes/ui_data.py` declares `GET /tickers/managed` 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 /trending
`services/api/routes/ui_data.py` declares `GET /trending` 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 /watchlist
`services/api/routes/ui_data.py` declares `GET /watchlist` 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 /weight-drift
`services/api/routes/analytics.py` declares `GET /weight-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 removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{full_path:path}
`services/api/server.py` declares `GET /{full_path:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{sector}/{agent}
`services/api/routes/prompts.py` declares `GET /{sector}/{agent}` 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 /tickers/managed/{sym}/toggle
`services/api/routes/ui_data.py` declares `PATCH /tickers/managed/{sym}/toggle` 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 /backfill
`services/api/routes/scheduler_api.py` declares `POST /backfill` 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 /chat
`services/api/routes/ui_data.py` declares `POST /chat` 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 /chat/stream
`services/api/routes/ui_data.py` declares `POST /chat/stream` 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 /daily-review
`services/api/routes/scheduler_api.py` declares `POST /daily-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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /deploy
`services/api/routes/prompts.py` declares `POST /deploy` 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 /forecast
`services/api/routes/scheduler_api.py` declares `POST /forecast` 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 /tickers/managed/{sym}
`services/api/routes/ui_data.py` declares `POST /tickers/managed/{sym}` 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 /tickers/managed/{sym}/generate-envelope
`services/api/routes/ui_data.py` declares `POST /tickers/managed/{sym}/generate-envelope` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /agents/tasks
`services/api/routes/ui_data.py` declares `PUT /agents/tasks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /agents/weights
`services/api/routes/ui_data.py` declares `PUT /agents/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: PUT /categories/{key}/tickers
`services/api/routes/ui_data.py` declares `PUT /categories/{key}/tickers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /tickers/managed
`services/api/routes/ui_data.py` declares `PUT /tickers/managed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /watchlist
`services/api/routes/ui_data.py` declares `PUT /watchlist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{sector}/{agent}
`services/api/routes/prompts.py` declares `PUT /{sector}/{agent}` 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: core/intelligence/rl/workflows/daily_review.py (1408 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: generate_sector_skeletons.py (1013 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/api/routes/ui_data.py (3597 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/backend/shared/schemas/feedback.py (1058 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/frontend/prototypes/home.jsx (1472 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/20724612-48fe-410b-929c-312625e8e271/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/20724612-48fe-410b-929c-312625e8e271/

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.