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

rehnmark75/TradeSystemV1-Moved

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

456 raw signals (0 security + 456 graph)

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

Complete repo analysis

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

JSON
Combined
50.4
/100
Security checks
50
0 findings
System graph
50
100.0% cov · 426 findings
Critical
17
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 17 High 95 Medium 65 Low 188 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 426 Crowd 0 Layer: Software 20 Frontend 4 Network 2 Hardware 12 Security 58 Cicd 1 Quality 223 Api 106
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 50.4/100 with 100.0% coverage. It contains 14525 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 456 findings — concentrated in quality (241), api (106), security (62). Risk profile is high: 21 critical, 96 high, 65 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in dev-app/config.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 80, 87
dev-app/config.py:80, 87 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in dev-app/dependencies.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
dev-app/dependencies.py:10
critical System graph security Secrets conf 1.00 Possible secret in optimization/rag_data_preparation.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
optimization/rag_data_preparation.py:53
critical System graph security Secrets conf 1.00 Possible secret in prod-app/config.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
prod-app/config.py:18
critical System graph security Secrets conf 1.00 Possible secret in stream-app/config.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
stream-app/config.py:6
critical System graph security Secrets conf 1.00 Possible secret in streamlit/config.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
streamlit/config.py:6
critical System graph security Secrets conf 1.00 Possible secret in worker/app/eurjpy_model_search.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/eurjpy_model_search.py:63
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in worker/app/forex_scanner/alerts/order_executor.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 1755, 1851, 1898, 1955
worker/app/forex_scanner/alerts/order_executor.py:1755, 1851, 1898, 1955 (4 hits)
critical System graph security Secrets conf 1.00 Possible secret in worker/app/forex_scanner/scripts/analyze_pair_performance.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/forex_scanner/scripts/analyze_pair_performance.py:78
critical System graph security Secrets conf 1.00 Possible secret in worker/app/forex_scanner/scripts/diag_audjpy_range_fade.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/forex_scanner/scripts/diag_audjpy_range_fade.py:390
critical System graph security Secrets conf 1.00 Possible secret in worker/app/forex_scanner/scripts/diag_range_fade_adx.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/forex_scanner/scripts/diag_range_fade_adx.py:85
critical System graph security Secrets conf 1.00 Possible secret in worker/app/forex_scanner/scripts/verify_claude.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
worker/app/forex_scanner/scripts/verify_claude.py:122
critical System graph security Secrets conf 1.00 Possible secret in worker/app/fx_xsec_momentum_probe.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/fx_xsec_momentum_probe.py:130
critical System graph security Secrets conf 1.00 Possible secret in worker/app/htf_edge_probe.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/htf_edge_probe.py:86
critical System graph security Secrets conf 1.00 Possible secret in worker/app/old_data/services/scanner_config.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
worker/app/old_data/services/scanner_config.py:1026
critical System graph security Secrets conf 1.00 Possible secret in worker/app/range_fade_diag3.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/range_fade_diag3.py:48
critical System graph security Secrets conf 1.00 Possible secret in worker/app/range_fade_width_sweep.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
worker/app/range_fade_width_sweep.py:102
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/docker-environment.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/docker-environment.md:156 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:633 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/broker/overview?days=7 (trading-ui/app/page.tsx:287)
`trading-ui/app/page.tsx:287` calls `GET /trading/api/broker/overview?days=7` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/broker/overview` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/chart/candles?${params} (trading-ui/components/CandlestickChart.tsx:311)
`trading-ui/components/CandlestickChart.tsx:311` calls `GET /trading/api/chart/candles?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/chart/candles` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/chart/epics?config_set=${configSet} (trading-ui/components/CandlestickChart.tsx:222)
`trading-ui/components/CandlestickChart.tsx:222` calls `GET /trading/api/chart/epics?config_set=${configSet}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/chart/epics` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/adx-regime/?days=${days} (trading-ui/app/forex/adx-regime/page.tsx:250)
`trading-ui/app/forex/adx-regime/page.tsx:250` calls `GET /trading/api/forex/adx-regime/?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/adx-regime` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/alert-data?${query}&env=${environment} (trading-ui/app/forex/alert-data/page.tsx:53)
`trading-ui/app/forex/alert-data/page.tsx:53` calls `GET /trading/api/forex/alert-data?${query}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/alert-data` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/alert-history/?${params.toString()}&env=${environment} (trading-ui/app/forex/alert-history/page.tsx:96)
`trading-ui/app/forex/alert-history/page.tsx:96` calls `GET /trading/api/forex/alert-history/?${params.toString()}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/alert-history` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/alert-history/?days=1&page=1&limit=5&status=All&strategy=All&pair=All&env=${environment} (trading-ui/app/page.tsx:282)
`trading-ui/app/page.tsx:282` calls `GET /trading/api/forex/alert-history/?days=1&page=1&limit=5&status=All&strategy=All&pair=All&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/analysis/?days=${analysisDays}&env=${environment} (trading-ui/app/forex/page.tsx:187)
`trading-ui/app/forex/page.tsx:187` calls `GET /trading/api/forex/analysis/?days=${analysisDays}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/analysis` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/analysis/?days=${days}&env=${environment} (trading-ui/app/forex/strategy/page.tsx:67)
`trading-ui/app/forex/strategy/page.tsx:67` calls `GET /trading/api/forex/analysis/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/analysis` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/backtests/?${params}&env=${environment} (trading-ui/app/forex/backtests/page.tsx:65)
`trading-ui/app/forex/backtests/page.tsx:65` calls `GET /trading/api/forex/backtests/?${params}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/backtests/executions/${executionId}/ (trading-ui/app/forex/backtests/[id]/page.tsx:55)
`trading-ui/app/forex/backtests/[id]/page.tsx:55` calls `GET /trading/api/forex/backtests/executions/${executionId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests/executions/<p>` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/backtests/jobs/${selectedJobId}/ (trading-ui/app/forex/backtests/page.tsx:105)
`trading-ui/app/forex/backtests/page.tsx:105` calls `GET /trading/api/forex/backtests/jobs/${selectedJobId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests/jobs/<p>` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/backtests/jobs/${selectedJobId}/ (trading-ui/app/forex/backtests/page.tsx:88)
`trading-ui/app/forex/backtests/page.tsx:88` calls `GET /trading/api/forex/backtests/jobs/${selectedJobId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests/jobs/<p>` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/breakeven-optimizer/?days=${days}&env=${environment}&strategy=${encodeURIComponent(strategyFilter)} (trading-ui/app/forex/breakeven-optimizer/page.tsx:94)
`trading-ui/app/forex/breakeven-optimizer/page.tsx:94` calls `GET /trading/api/forex/breakeven-optimizer/?days=${days}&env=${environment}&strategy=${encodeURIComponent(strategyFilter)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path use…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/claude-rejections/?${params.toString()} (trading-ui/app/forex/claude-rejections/page.tsx:206)
`trading-ui/app/forex/claude-rejections/page.tsx:206` calls `GET /trading/api/forex/claude-rejections/?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/claude-rejections` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/economic-calendar?${params.toString()} (trading-ui/app/forex/economic-calendar/page.tsx:166)
`trading-ui/app/forex/economic-calendar/page.tsx:166` calls `GET /trading/api/forex/economic-calendar?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/economic-calendar` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/entry-timing/?days=${days}&env=${environment}&strategy=${encodeURIComponent(strategyFilter)} (trading-ui/app/forex/entry-timing/page.tsx:123)
`trading-ui/app/forex/entry-timing/page.tsx:123` calls `GET /trading/api/forex/entry-timing/?days=${days}&env=${environment}&strategy=${encodeURIComponent(strategyFilter)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matchin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/filter-effectiveness/?days=${days}&env=${environment} (trading-ui/app/forex/filter-effectiveness/page.tsx:71)
`trading-ui/app/forex/filter-effectiveness/page.tsx:71` calls `GET /trading/api/forex/filter-effectiveness/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/filter-ef…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/htf-analysis/?days=${days}&env=${environment} (trading-ui/app/forex/htf-analysis/page.tsx:130)
`trading-ui/app/forex/htf-analysis/page.tsx:130` calls `GET /trading/api/forex/htf-analysis/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/htf-analysis` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/mae-analysis/?days=${days}&env=${environment} (trading-ui/app/forex/mae-analysis/page.tsx:123)
`trading-ui/app/forex/mae-analysis/page.tsx:123` calls `GET /trading/api/forex/mae-analysis/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/mae-analysis` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/market-conditions?${params.toString()} (trading-ui/app/forex/market-conditions/page.tsx:237)
`trading-ui/app/forex/market-conditions/page.tsx:237` calls `GET /trading/api/forex/market-conditions?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/market-conditions` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/market-intelligence/?env=${environment} (trading-ui/app/page.tsx:286)
`trading-ui/app/page.tsx:286` calls `GET /trading/api/forex/market-intelligence/?env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/market-intelligence` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/monitor-outcomes/?days=${days}&env=${environment} (trading-ui/app/forex/monitor-outcomes/page.tsx:114)
`trading-ui/app/forex/monitor-outcomes/page.tsx:114` calls `GET /trading/api/forex/monitor-outcomes/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/monitor-outcomes…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/overview/?days=${overviewDays}&env=${environment} (trading-ui/app/forex/page.tsx:169)
`trading-ui/app/forex/page.tsx:169` calls `GET /trading/api/forex/overview/?days=${overviewDays}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/overview` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/overview/?days=7&env=${environment} (trading-ui/app/page.tsx:285)
`trading-ui/app/page.tsx:285` calls `GET /trading/api/forex/overview/?days=7&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/overview` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/smc-rejections/conflicts/?days=${days}&env=${environment} (trading-ui/app/forex/smc-rejections/page.tsx:157)
`trading-ui/app/forex/smc-rejections/page.tsx:157` calls `GET /trading/api/forex/smc-rejections/conflicts/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/smc-reject…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/smc-rejections/list/?${params.toString()}&env=${environment} (trading-ui/app/forex/smc-rejections/page.tsx:154)
`trading-ui/app/forex/smc-rejections/page.tsx:154` calls `GET /trading/api/forex/smc-rejections/list/?${params.toString()}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/smc-rej…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/smc-rejections/options/?env=${environment} (trading-ui/app/forex/smc-rejections/page.tsx:136)
`trading-ui/app/forex/smc-rejections/page.tsx:136` calls `GET /trading/api/forex/smc-rejections/options/?env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/smc-rejections/options` I…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/smc-rejections/outcomes/?days=${days}&env=${environment} (trading-ui/app/forex/smc-rejections/page.tsx:160)
`trading-ui/app/forex/smc-rejections/page.tsx:160` calls `GET /trading/api/forex/smc-rejections/outcomes/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/smc-rejecti…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/smc-rejections/stats/?days=${days}&env=${environment} (trading-ui/app/forex/smc-rejections/page.tsx:153)
`trading-ui/app/forex/smc-rejections/page.tsx:153` calls `GET /trading/api/forex/smc-rejections/stats/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/smc-rejections…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/strategy-rejections/list?${params} (trading-ui/app/forex/strategy-rejections/page.tsx:240)
`trading-ui/app/forex/strategy-rejections/page.tsx:240` calls `GET /trading/api/forex/strategy-rejections/list?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/strategy-rejections/list` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/strategy-rejections/options (trading-ui/app/forex/strategy-rejections/page.tsx:205)
`trading-ui/app/forex/strategy-rejections/page.tsx:205` calls `GET /trading/api/forex/strategy-rejections/options` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/strategy-rejections/options` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/strategy-rejections/stats?${params} (trading-ui/app/forex/strategy-rejections/page.tsx:216)
`trading-ui/app/forex/strategy-rejections/page.tsx:216` calls `GET /trading/api/forex/strategy-rejections/stats?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/strategy-rejections/stats` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/strategy-rejections/top-stages?${params} (trading-ui/app/forex/strategy-rejections/page.tsx:217)
`trading-ui/app/forex/strategy-rejections/page.tsx:217` calls `GET /trading/api/forex/strategy-rejections/top-stages?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/strategy-rejections/to…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/trade-analysis/chart-data/?tradeId=${id}&env=${environment} (trading-ui/app/forex/trade-analysis/page.tsx:125)
`trading-ui/app/forex/trade-analysis/page.tsx:125` calls `GET /trading/api/forex/trade-analysis/chart-data/?tradeId=${id}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/trade-an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/trade-analysis/postmortem/?tradeId=${id}&env=${env} (trading-ui/app/forex/trade-analysis/page.tsx:97)
`trading-ui/app/forex/trade-analysis/page.tsx:97` calls `GET /trading/api/forex/trade-analysis/postmortem/?tradeId=${id}&env=${env}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/trade-analysis/po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/trade-analysis/trades/?${params} (trading-ui/app/forex/trade-analysis/page.tsx:76)
`trading-ui/app/forex/trade-analysis/page.tsx:76` calls `GET /trading/api/forex/trade-analysis/trades/?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/trade-analysis/trades` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/trades/?days=${days}&env=${environment} (trading-ui/app/forex/trade-performance/page.tsx:107)
`trading-ui/app/forex/trade-performance/page.tsx:107` calls `GET /trading/api/forex/trades/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/trades` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/unfilled-orders/ (trading-ui/app/forex/unfilled-orders/page.tsx:109)
`trading-ui/app/forex/unfilled-orders/page.tsx:109` calls `GET /trading/api/forex/unfilled-orders/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/unfilled-orders` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/validator-rejections/list/?${params}&env=${environment} (trading-ui/app/forex/validator-rejections/page.tsx:186)
`trading-ui/app/forex/validator-rejections/page.tsx:186` calls `GET /trading/api/forex/validator-rejections/list/?${params}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/valida…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/validator-rejections/lpf/?days=${days}&env=${environment} (trading-ui/app/forex/validator-rejections/page.tsx:187)
`trading-ui/app/forex/validator-rejections/page.tsx:187` calls `GET /trading/api/forex/validator-rejections/lpf/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/vali…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/validator-rejections/options/?env=${environment} (trading-ui/app/forex/validator-rejections/page.tsx:173)
`trading-ui/app/forex/validator-rejections/page.tsx:173` calls `GET /trading/api/forex/validator-rejections/options/?env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/validator-rej…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/forex/validator-rejections/stats/?days=${days}&env=${environment} (trading-ui/app/forex/validator-rejections/page.tsx:185)
`trading-ui/app/forex/validator-rejections/page.tsx:185` calls `GET /trading/api/forex/validator-rejections/stats/?days=${days}&env=${environment}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/va…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/infra/alerts/active (trading-ui/app/page.tsx:278)
`trading-ui/app/page.tsx:278` calls `GET /trading/api/infra/alerts/active` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/infra/alerts/active` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/infra/containers (trading-ui/app/page.tsx:279)
`trading-ui/app/page.tsx:279` calls `GET /trading/api/infra/containers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/infra/containers` 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 /trading/api/infra/containers/${encodeURIComponent(containerName)}/logs?lines=${lines} (trading-ui/components/ops/ContainerLogsDrawer.tsx:20)
`trading-ui/components/ops/ContainerLogsDrawer.tsx:20` calls `GET /trading/api/infra/containers/${encodeURIComponent(containerName)}/logs?lines=${lines}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/in…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/infra/status (trading-ui/app/page.tsx:277)
`trading-ui/app/page.tsx:277` calls `GET /trading/api/infra/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/infra/status` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/market/holiday (trading-ui/app/forex/page.tsx:159)
`trading-ui/app/forex/page.tsx:159` calls `GET /trading/api/market/holiday` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/market/holiday` 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 /trading/api/market/holiday (trading-ui/app/page.tsx:288)
`trading-ui/app/page.tsx:288` calls `GET /trading/api/market/holiday` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/market/holiday` 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 /trading/api/market/holidays?days=${holidayDays} (trading-ui/app/forex/economic-calendar/page.tsx:181)
`trading-ui/app/forex/economic-calendar/page.tsx:181` calls `GET /trading/api/market/holidays?days=${holidayDays}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/market/holidays` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/market/regime (trading-ui/app/page.tsx:276)
`trading-ui/app/page.tsx:276` calls `GET /trading/api/market/regime` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/market/regime` 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 /trading/api/stream/operations/recent?limit=5 (trading-ui/app/page.tsx:281)
`trading-ui/app/page.tsx:281` calls `GET /trading/api/stream/operations/recent?limit=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/stream/operations/recent` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /trading/api/stream/summary (trading-ui/app/page.tsx:280)
`trading-ui/app/page.tsx:280` calls `GET /trading/api/stream/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/stream/summary` 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: POST /trading/api/forex/backtests/ (trading-ui/app/forex/backtests/page.tsx:154)
`trading-ui/app/forex/backtests/page.tsx:154` calls `POST /trading/api/forex/backtests/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /trading/api/forex/backtests/jobs/${jobId}/${action}/ (trading-ui/app/forex/backtests/page.tsx:182)
`trading-ui/app/forex/backtests/page.tsx:182` calls `POST /trading/api/forex/backtests/jobs/${jobId}/${action}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/forex/backtests/jobs/<p>/<p>` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /trading/api/orders/place (trading-ui/components/PlaceOrderForm.tsx:54)
`trading-ui/components/PlaceOrderForm.tsx:54` calls `POST /trading/api/orders/place` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trading/api/orders/place` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete` without auth dependency — dev-app/routers/trailing_config_router.py:232
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trailing_config_router.py:232 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `remove_position` without auth dependency — dev-app/routers/virtual_stop_loss_router.py:121
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/virtual_stop_loss_router.py:121 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `stop_tracking_trade` without auth dependency — stream-app/routers/stream_router.py:146
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
stream-app/routers/stream_router.py:146 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `acknowledge_alert` without auth dependency — system-monitor/app/api/routes.py:291
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
system-monitor/app/api/routes.py:291 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_position_manual` without auth dependency — dev-app/routers/virtual_stop_loss_router.py:159
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/virtual_stop_loss_router.py:159 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `block_root` without auth dependency — dev-app/main.py:856
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/main.py:856 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `block_root` without auth dependency — prod-app/main.py:135
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
prod-app/main.py:135 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `calculate_complete_pnl` without auth dependency — dev-app/routers/trading_analytics_router.py:57
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:57 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_and_close_positions_endpoint` without auth dependency — dev-app/routers/position_closer_router.py:58
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/position_closer_router.py:58 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_and_close_positions_endpoint` without auth dependency — prod-app/routers/position_closer_router.py:44
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
prod-app/routers/position_closer_router.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `claude_analyze_watchlist` without auth dependency — fastapi-general/app/main.py:98
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fastapi-general/app/main.py:98 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `claude_analyze` without auth dependency — fastapi-general/app/main.py:55
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
fastapi-general/app/main.py:55 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `correlate_activity_based_pnl` without auth dependency — dev-app/routers/trading_analytics_router.py:186
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:186 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fetch_ig_transactions` without auth dependency — dev-app/routers/trading_analytics_router.py:392
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:392 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `inspect_trade_log_entries` without auth dependency — dev-app/routers/trading_analytics_router.py:1340
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:1340 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `invalidate_cache` without auth dependency — dev-app/routers/trailing_config_router.py:225
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trailing_config_router.py:225 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `manual_close_all_positions_endpoint` without auth dependency — dev-app/routers/position_closer_router.py:91
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/position_closer_router.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `manual_close_all_positions_endpoint` without auth dependency — prod-app/routers/position_closer_router.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.
prod-app/routers/position_closer_router.py:76 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `manual_evaluate` without auth dependency — dev-app/routers/manual_trigger_router.py:29
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/manual_trigger_router.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_positions` without auth dependency — dev-app/routers/virtual_stop_loss_router.py:52
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/virtual_stop_loss_router.py:52 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resolve_alert` without auth dependency — system-monitor/app/api/routes.py:310
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
system-monitor/app/api/routes.py:310 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `restart_container` without auth dependency — system-monitor/app/api/routes.py:189
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
system-monitor/app/api/routes.py:189 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_stream` without auth dependency — stream-app/routers/stream_router.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.
stream-app/routers/stream_router.py:28 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stop_stream` without auth dependency — stream-app/routers/stream_router.py:67
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
stream-app/routers/stream_router.py:67 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_activity_extraction` without auth dependency — dev-app/routers/trading_analytics_router.py:862
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:862 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_database_updates` without auth dependency — dev-app/routers/trading_analytics_router.py:1446
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:1446 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_notification` without auth dependency — system-monitor/app/api/routes.py:328
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
system-monitor/app/api/routes.py:328 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_trade` without auth dependency — stream-app/routers/stream_router.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.
stream-app/routers/stream_router.py:108 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_database_structure` without auth dependency — dev-app/routers/trading_analytics_router.py:965
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:965 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_pnl_calculations` without auth dependency — dev-app/routers/trading_analytics_router.py:1083
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:1083 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_trade_correlations` without auth dependency — dev-app/routers/trading_analytics_router.py:1237
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trading_analytics_router.py:1237 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `upsert` without auth dependency — dev-app/routers/trailing_config_router.py:191
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dev-app/routers/trailing_config_router.py:191 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — trading-ui/app/api/forex/smc-rejections/outcomes/route.ts:11
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 — trading-ui/app/api/orders/place/route.ts:178
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 — trading-ui/app/broker/page.tsx:108
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 — trading-ui/app/forex/smc-rejections/page.tsx:153
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 — trading-ui/app/forex/trade-analysis/page.tsx:97
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 — trading-ui/app/forex/validator-rejections/page.tsx:185
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 — trading-ui/app/infrastructure/page.tsx:109
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 — trading-ui/app/market/page.tsx:78
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 — trading-ui/app/page.tsx:278
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 — trading-ui/app/settings/audit/page.tsx:29
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 — trading-ui/app/settings/page.tsx:30
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 — trading-ui/app/settings/strategy/page.tsx:846
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 — trading-ui/app/signals/page.tsx:456
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 — trading-ui/app/stocks/[ticker]/page.tsx:311
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 — trading-ui/app/sw.js/route.ts:49
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 — trading-ui/app/system/log-search/page.tsx:179
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 — trading-ui/app/system/page.tsx:507
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 — trading-ui/app/watchlists/page.tsx:256
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 — trading-ui/components/CandlestickChart.tsx:311
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 — trading-ui/components/settings/ParameterContextPanel.tsx:50
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 — trading-ui/components/settings/ScannerContextPanel.tsx:57
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 — trading-ui/hooks/settings/usePairOverrides.ts:47
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 — trading-ui/hooks/settings/useSnapshots.ts:58
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 — trading-ui/hooks/settings/useTrailingConfig.ts:64
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 — trading-ui/hooks/settings/useTrailingRatios.ts:70
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — trading-ui/public/sw.js:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/db-expert.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agents/db-expert.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/smc-simple-config-schema.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agents/smc-simple-config-schema.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: AGENTS.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
AGENTS.md VerificationAgents md
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, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: nginx:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
nginx/Dockerfile:1 containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: economic-calendar/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: fastapi-general/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: nginx/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: stock-scanner/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: streamlit/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: system-monitor/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: trading-ui/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: worker/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in economic-calendar/app/main.py:122
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
economic-calendar/app/main.py:122 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in system-monitor/app/main.py:239
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
system-monitor/app/main.py:239 Cors wildcard
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — rag_interface.py:94
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/search_ig_markets.py:27
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — stock-scanner/app/stock_scanner/bt_stocks.py:133
`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 — stream-app/validation/check_actual_corruption.py:79
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — stream-app/validation/correct_specific_entries.py:91
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — stream-app/validation/fill_specific_gap.py:101
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — streamlit/services/backtest_runner_service.py:289
`subprocess.Popen(...)` 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 — worker/app/forex_scanner/scripts/ablate_mean_reversion.py:137
`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 — worker/app/forex_scanner/scripts/ablate_range_fade.py:116
`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 — worker/app/forex_scanner/scripts/ablate_smc_simple.py:211
`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 — worker/app/forex_scanner/scripts/ablate_xau_gold.py:164
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — worker/app/forex_scanner/scripts/analysis/smc_simple/run_smc_eurusd_quality_sweep.py:123
`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 — worker/app/forex_scanner/scripts/diag_audjpy_range_fade.py:140
`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 — worker/app/forex_scanner/scripts/eval_range_fade.py:61
`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 — worker/app/forex_scanner/scripts/sweep_gbpusd_range_fade.py:68
`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 — worker/app/search_ig_markets.py:27
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 266 placeholder/mock markers across 106 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
worker/app/forex_scanner/count_patterns.sh Ports
medium System graph network Security conf 1.00 Privileged port 46 in use
Port 46 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
worker/app/forex_scanner/count_patterns.sh Ports
low System graph quality Maintenance conf 1.00 33 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Integrity conf 1.00 70 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `API_SUBSCRIPTION_KEY`, `AUTO_PAUSE_ENABLED`, `AUTO_TRADER_INTERVAL_SECONDS`, `BACKTEST_USE_LEGACY_SIMULATOR`, `BREAKEVEN_MONITOR_DRY_RUN`, `BREAKEVEN_MONITOR_INTERVAL_SECONDS`, `BROKER_CREATE_POSITION_COOLDOWN_SECONDS` + 62 mo…
config drift
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 6777 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 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 5, 18
trading-ui/Dockerfile:1, 5, 18 (3 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 7 occurrences 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.
6 files, 7 locations
stock-scanner/Dockerfile:2, 14 (2 hits)
economic-calendar/Dockerfile:1
fastapi-general/Dockerfile:1
streamlit/Dockerfile:2
system-monitor/Dockerfile:1
worker/Dockerfile:2
containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — trading-ui/components/ops/ContainerLogsDrawer.tsx:58
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — trading-ui/components/settings/SaveModal.tsx:55
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — trading-ui/components/settings/SnapshotDiffView.tsx:68
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — trading-ui/components/settings/SnapshotPanel.tsx:116
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 security security conf 1.00 Insecure pattern 'debug_true' in worker/app/old_data/OldScans/trade_scan copy.py:1116
Found a known-risky pattern (debug_true). Review and replace if possible.
worker/app/old_data/OldScans/trade_scan copy.py:1116 Debug true
low System graph quality Tests conf 1.00 Low test-to-source ratio
141 tests / 1086 src (ratio 0.13).
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: test_time_controls.py:test_closure_logic, test_time_controls.py:test_closure 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.
19 occurrences
repo-level (19 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: prod-app/services/keyvault.py:get_secret, worker/app/old_data/services/keyvault.py:get_secret, stream-app/services/keyvault.py:get_secret, streamlit/services/keyvault.py:get_secret This is *the* AI-coder failure mode (4× more duplication in vibe-code…
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: trading-ui/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
trading-ui/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_calculate_confidence_legacy` in worker/app/forex_scanner/core/strategies/base_strategy.py:103
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 `_enhance_signal_metadata_v2` in worker/app/forex_scanner/core/processing/signal_processor.py:428
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 `_merge_enhanced_config_with_legacy` in worker/app/forex_scanner/archive/disabled_strategies/bb_supertrend_strategy.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 `_validate_ema_signal_legacy` in worker/app/forex_scanner/alerts/claude_api.py:1581
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 `backtest_v1` in worker/app/forex_scanner/core/backtest_scanner.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 `backtest_v1` in worker/app/forex_scanner/core/trading/backtest_trading_orchestrator.py:393
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 stock-scanner/app/stock_scanner/core/news/sentiment_analyzer.py:206
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 stock-scanner/app/stock_scanner/scanners/scanner_manager.py:733
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 stream-app/maintenance/mark_old_failed_gaps.py:23
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 `df_copy` in streamlit/components/tabs/ema_rejections_tab.py:219
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 `df_copy` in streamlit/components/tabs/smc_rejections_tab.py:859
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 `df_copy` in worker/app/forex_scanner/archive/disabled_helpers/ichimoku_indicator_calculator.py:90
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 `df_copy` in worker/app/forex_scanner/archive/disabled_helpers/macd_indicator_calculator.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 `df_copy` in worker/app/forex_scanner/archive/disabled_helpers/macd_mtf_analyzer.py:233
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 `df_copy` in worker/app/forex_scanner/archive/disabled_helpers/mean_reversion_indicator_calculator.py:130
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 `df_copy` in worker/app/forex_scanner/archive/disabled_helpers/smc_mtf_analyzer.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 quality Integrity conf 1.00 Old/deprecated-named symbol `df_copy` in worker/app/forex_scanner/core/intelligence/order_flow_analyzer.py:284
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 `df_copy` in worker/app/old_data/services/enhance_data.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 `enhanced_backup` in streamlit/pages/forex_documentation.py:507
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 `enhanced_v1` in worker/app/forex_scanner/core/scanner.py:1078
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 `files_to_backup` in worker/app/forex_scanner/scripts/fix_alert_saver.py:17
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `final_backup` in worker/app/forex_scanner/scripts/alert_fx1.py:317
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 `kama_old` in worker/app/forex_scanner/core/strategies/kama_v2_strategy.py:324
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 `kama_v2` in worker/app/forex_scanner/core/signal_detector.py:1085
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 `live_v1` in worker/app/forex_scanner/validation/pipeline_consistency_validator.py:719
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 `s_copy` in streamlit/pages/tvchart.py:1356
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 `signals_london_open_breakout_v2` in worker/app/eurjpy_model_search.py:416
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 `smc_15m_v2` in smc_deep_analysis.py:477
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 `smc_15m_v2` in worker/app/info/extract_smc_signals.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 `smc_simple_v2` in worker/app/forex_scanner/alerts/analysis/prompt_builder.py:596
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 `smc_simple_v2` in worker/app/forex_scanner/alerts/analysis/prompts/smc_simple_v2.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 `smc_simple_v2` in worker/app/forex_scanner/core/strategies/smc_simple_v2_strategy.py:73
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 `smc_strategy_v2` in trading-ui/app/api/settings/strategy/smc/snapshots/route.ts:23
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 `smc_structure_strategy_v2` in smc_strategy_fixes_v2.6.0.py:270
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: add_custom_rule
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/exclusion_filters.py:357
low System graph software Dead code conf 1.00 Possibly dead Python function: add_filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/exclusion_filters.py:353
low System graph software Dead code conf 1.00 Possibly dead Python function: build_confluence_factors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/base_scanner.py:760
low System graph software Dead code conf 1.00 Possibly dead Python function: call_position_closer_endpoint
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
prod-app/main.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: classify_pnl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/analysis/sltp_calibration.py:306
low System graph software Dead code conf 1.00 Possibly dead Python function: core_score
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/analysis/grading_replay.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_cleanup_task
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
economic-calendar/app/scraper/scheduler.py:154
low System graph software Dead code conf 1.00 Possibly dead Python function: directional_filters
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
smc_strategy_fixes_v2.6.0.py:181
low System graph software Dead code conf 1.00 Possibly dead Python function: drop_tables
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
economic-calendar/app/database/connection.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: enrich_signals_with_news
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/scanner_manager.py:1409
low System graph software Dead code conf 1.00 Possibly dead Python function: enrich_single_signal_news
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/scanner_manager.py:1498
low System graph software Dead code conf 1.00 Possibly dead Python function: expire_old_signals
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/scanner_manager.py:733
low System graph software Dead code conf 1.00 Possibly dead Python function: health_check_task
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
economic-calendar/app/scraper/scheduler.py:165
low System graph software Dead code conf 1.00 Possibly dead Python function: htf_strength_enforcement
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
smc_strategy_fixes_v2.6.0.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: optimal_filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
smc_strategy_fixes_v2.6.0.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: premium_zone_filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
smc_strategy_fixes_v2.6.0.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: run_single_scanner
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/scanner_manager.py:566
low System graph software Dead code conf 1.00 Possibly dead Python function: swing_core
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/analysis/swing_replay.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: update_signal_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
stock-scanner/app/stock_scanner/scanners/scanner_manager.py:702
low System graph software Dead code conf 1.00 Possibly dead Python function: weekly_scrape_task
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
economic-calendar/app/scraper/scheduler.py:119
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 quality Integrity conf 1.00 Stub function `fx15m_default` (body is just `pass`/`return`) — worker/app/forex_scanner/archive/disabled_strategies/bb_supertrend_strategy.py:56
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `reset_cooldowns` (body is just `pass`/`return`) — worker/app/forex_scanner/core/strategies/smc_simple_v2_strategy.py:108
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `start` (body is just `pass`/`return`) — worker/app/forex_scanner/core/concurrent_execution/backtest_execution_manager.py:707
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: DELETE /stream/track-trade/{deal_id}
`stream-app/routers/stream_router.py` declares `DELETE /stream/track-trade/{deal_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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`prod-app/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /backfill/gaps
`stream-app/main.py` declares `GET /backfill/gaps` 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 /backfill/status
`stream-app/main.py` declares `GET /backfill/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /deals/pnl-calculation-status
`dev-app/routers/trading_analytics_router.py` declares `GET /deals/pnl-calculation-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /events
`economic-calendar/app/api/routes.py` declares `GET /events` 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 /events/currency/{currency}
`economic-calendar/app/api/routes.py` declares `GET /events/currency/{currency}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /events/impact-analysis
`economic-calendar/app/api/routes.py` declares `GET /events/impact-analysis` 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 /events/upcoming
`economic-calendar/app/api/routes.py` declares `GET /events/upcoming` 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
`prod-app/routers/position_closer_router.py` declares `GET /history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ig/connection-test
`dev-app/routers/trading_analytics_router.py` declares `GET /ig/connection-test` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /monitor-status
`dev-app/main.py` declares `GET /monitor-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /next-closure-time
`prod-app/routers/position_closer_router.py` declares `GET /next-closure-time` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /performance/summary
`dev-app/routers/trading_analytics_router.py` declares `GET /performance/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /scrape/logs
`economic-calendar/app/api/routes.py` declares `GET /scrape/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 /sl-tp
`prod-app/routers/sl_tp_router.py` declares `GET /sl-tp` 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 /statistics
`dev-app/routers/trading_analytics_router.py` declares `GET /statistics` 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 /stream/alerts/recent
`stream-app/routers/stream_router.py` declares `GET /stream/alerts/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 /stream/candle/latest/{epic}
`stream-app/routers/stream_router.py` declares `GET /stream/candle/latest/{epic}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stream/candles/{epic}
`stream-app/routers/stream_router.py` declares `GET /stream/candles/{epic}` 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 /stream/health
`stream-app/routers/stream_router.py` declares `GET /stream/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stream/logs/recent
`stream-app/routers/stream_router.py` declares `GET /stream/logs/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 /stream/operations/recent
`stream-app/routers/stream_router.py` declares `GET /stream/operations/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 /stream/status
`stream-app/routers/stream_router.py` declares `GET /stream/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stream/system/summary
`stream-app/routers/stream_router.py` declares `GET /stream/system/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 /stream/track-trade
`stream-app/routers/stream_router.py` declares `GET /stream/track-trade` 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 /transactions/today
`dev-app/routers/trading_analytics_router.py` declares `GET /transactions/today` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /validate
`prod-app/main.py` declares `GET /validate` 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 /
`prod-app/main.py` declares `POST /` 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 /check-and-close
`prod-app/routers/position_closer_router.py` declares `POST /check-and-close` 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 /claude/analyze
`fastapi-general/app/main.py` declares `POST /claude/analyze` 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 /claude/analyze-watchlist
`fastapi-general/app/main.py` declares `POST /claude/analyze-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: POST /deals/calculate-complete-pnl
`dev-app/routers/trading_analytics_router.py` declares `POST /deals/calculate-complete-pnl` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /deals/correlate-activities
`dev-app/routers/trading_analytics_router.py` declares `POST /deals/correlate-activities` 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: POST /deals/test-activity-extraction
`dev-app/routers/trading_analytics_router.py` declares `POST /deals/test-activity-extraction` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /inspect/trade-log
`dev-app/routers/trading_analytics_router.py` declares `POST /inspect/trade-log` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /manual-close-all
`prod-app/routers/position_closer_router.py` declares `POST /manual-close-all` 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 /place-order
`prod-app/routers/orders_router.py` declares `POST /place-order` 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 /scheduler/pause/{job_id}
`economic-calendar/app/api/routes.py` declares `POST /scheduler/pause/{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: POST /scheduler/resume/{job_id}
`economic-calendar/app/api/routes.py` declares `POST /scheduler/resume/{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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /scrape/manual
`economic-calendar/app/api/routes.py` declares `POST /scrape/manual` 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 /stream/start-stream
`stream-app/routers/stream_router.py` declares `POST /stream/start-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 /stream/stop-stream
`stream-app/routers/stream_router.py` declares `POST /stream/stop-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 /stream/track-trade/{deal_id}
`stream-app/routers/stream_router.py` declares `POST /stream/track-trade/{deal_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /test/database-updates
`dev-app/routers/trading_analytics_router.py` declares `POST /test/database-updates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /transactions/fetch-ig
`dev-app/routers/trading_analytics_router.py` declares `POST /transactions/fetch-ig` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /transactions/upload
`dev-app/routers/trading_analytics_router.py` declares `POST /transactions/upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /verify/database-structure
`dev-app/routers/trading_analytics_router.py` declares `POST /verify/database-structure` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /verify/pnl-calculations
`dev-app/routers/trading_analytics_router.py` declares `POST /verify/pnl-calculations` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /verify/trade-correlations
`dev-app/routers/trading_analytics_router.py` declares `POST /verify/trade-correlations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: dev-app/enhanced_trade_processor.py (1194 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dev-app/main.py (1281 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dev-app/routers/orders_router.py (1757 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dev-app/routers/trade_analysis_router.py (1487 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dev-app/routers/trading_analytics_router.py (1692 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.

Showing first 300 of 359. Refine filters or use the findings page for deep search.

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/a0235066-2b97-4ab8-8db8-c4dfafff4e44/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a0235066-2b97-4ab8-8db8-c4dfafff4e44/

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.