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

Thepluscode/NexusTradeAI

https://github.com/Thepluscode/NexusTradeAI · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

418 raw signals (0 security + 418 graph)

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

Complete repo analysis

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

JSON
Combined
48.6
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 395 findings
Critical
5
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 5 High 115 Medium 32 Low 186 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 395 Crowd 0 Layer: Software 14 Frontend 84 Hardware 1 Security 65 Cicd 3 Quality 99 Api 129

Showing 337 of 395 actionable findings. 418 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 3 occurrences Possible secret in clients/bot-dashboard/src/pages/DocsPage.tsx
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 437, 468, 619
clients/bot-dashboard/src/pages/DocsPage.tsx:437, 468, 619 (3 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in clients/desktop-app/src/renderer/pages/RegisterPage.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 95, 96, 98
clients/desktop-app/src/renderer/pages/RegisterPage.tsx:95, 96, 98 (3 hits)
critical System graph security Secrets conf 1.00 3 occurrences Possible secret in data-infrastructure/scripts/deploy-infrastructure.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 260, 312, 382
data-infrastructure/scripts/deploy-infrastructure.sh:260, 312, 382 (3 hits)
critical System graph security Secrets conf 1.00 Possible secret in shared/constants/api-endpoints.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
shared/constants/api-endpoints.js:13
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in shared/README.md
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 95, 101
shared/README.md:95, 101 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://localhost:3002/orders/${orderId} (web-app/src/components/TradingInterface.js:128)
`web-app/src/components/TradingInterface.js:128` calls `DELETE http://localhost:3002/orders/${orderId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders/<p>` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://localhost:3002/orders/${req.params.orderId} (docs/archive/legacy-dir/trading-server.js:129)
`docs/archive/legacy-dir/trading-server.js:129` calls `DELETE http://localhost:3002/orders/${req.params.orderId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders/<p>` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000 (tests/legacy/test-exports-fix.js:19)
`tests/legacy/test-exports-fix.js:19` calls `GET http://localhost:3000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3000` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000 (tests/legacy/test-frontend-fixes.js:118)
`tests/legacy/test-frontend-fixes.js:118` calls `GET http://localhost:3000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3000` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/index.js (tests/legacy/test-exports-fix.js:42)
`tests/legacy/test-exports-fix.js:42` calls `GET http://localhost:3000/index.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3000/index.js` If this points at an external API, prefix it with `https…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/account (docs/archive/legacy-dir/trading-server.js:63)
`docs/archive/legacy-dir/trading-server.js:63` calls `GET http://localhost:3002/account` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/account` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/account (web-app/src/components/TradingInterface.js:48)
`web-app/src/components/TradingInterface.js:48` calls `GET http://localhost:3002/account` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/account` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/health (tests/legacy/test-enhanced-frontend.js:120)
`tests/legacy/test-enhanced-frontend.js:120` calls `GET http://localhost:3002/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/health` If this points at an external API, prefix it with `ht…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/health (tests/legacy/test-real-market-data.js:17)
`tests/legacy/test-real-market-data.js:17` calls `GET http://localhost:3002/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/health` If this points at an external API, prefix it with `http…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices (docs/archive/legacy-dir/trading-server.js:96)
`docs/archive/legacy-dir/trading-server.js:96` calls `GET http://localhost:3002/market-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/market-prices` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices (tests/legacy/test-enhanced-frontend.js:149)
`tests/legacy/test-enhanced-frontend.js:149` calls `GET http://localhost:3002/market-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/market-prices` If this points at an external API, pref…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices (tests/legacy/test-frontend-fixes.js:102)
`tests/legacy/test-frontend-fixes.js:102` calls `GET http://localhost:3002/market-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/market-prices` If this points at an external API, prefix …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices (tests/legacy/test-real-market-data.js:25)
`tests/legacy/test-real-market-data.js:25` calls `GET http://localhost:3002/market-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/market-prices` If this points at an external API, prefix…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices (web-app/src/components/TradingInterface.js:38)
`web-app/src/components/TradingInterface.js:38` calls `GET http://localhost:3002/market-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/market-prices` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/market-prices/AAPL (tests/legacy/test-real-market-data.js:38)
`tests/legacy/test-real-market-data.js:38` calls `GET http://localhost:3002/market-prices/AAPL` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3002/market-prices/aapl` If this points at an external A…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/orders (docs/archive/legacy-dir/trading-server.js:85)
`docs/archive/legacy-dir/trading-server.js:85` calls `GET http://localhost:3002/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/orders (web-app/src/components/TradingInterface.js:68)
`web-app/src/components/TradingInterface.js:68` calls `GET http://localhost:3002/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/positions (docs/archive/legacy-dir/trading-server.js:74)
`docs/archive/legacy-dir/trading-server.js:74` calls `GET http://localhost:3002/positions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/positions` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3002/positions (web-app/src/components/TradingInterface.js:58)
`web-app/src/components/TradingInterface.js:58` calls `GET http://localhost:3002/positions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/positions` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/analytics/alerts (services/dashboard/server.js:543)
`services/dashboard/server.js:543` calls `GET http://localhost:3003/api/analytics/alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/analytics/alerts` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/analytics/ratios (services/dashboard/server.js:522)
`services/dashboard/server.js:522` calls `GET http://localhost:3003/api/analytics/ratios` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/analytics/ratios` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/analytics/risk-report (services/dashboard/server.js:472)
`services/dashboard/server.js:472` calls `GET http://localhost:3003/api/analytics/risk-report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/analytics/risk-report` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/analytics/var (services/dashboard/server.js:503)
`services/dashboard/server.js:503` calls `GET http://localhost:3003/api/analytics/var` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/analytics/var` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/banking/balance/demo-user-123 (tests/legacy/test-banking-integration.js:120)
`tests/legacy/test-banking-integration.js:120` calls `GET http://localhost:3003/api/banking/balance/demo-user-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3003/api/banking/balance/demo-user-12…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/banking/balance/demo-user-123 (tests/legacy/test-banking-integration.js:42)
`tests/legacy/test-banking-integration.js:42` calls `GET http://localhost:3003/api/banking/balance/demo-user-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3003/api/banking/balance/demo-user-123…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/banking/limits/demo-user-123 (tests/legacy/test-banking-integration.js:127)
`tests/legacy/test-banking-integration.js:127` calls `GET http://localhost:3003/api/banking/limits/demo-user-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3003/api/banking/limits/demo-user-123`…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/banking/transactions/demo-user-123?limit=3 (tests/legacy/test-banking-integration.js:50)
`tests/legacy/test-banking-integration.js:50` calls `GET http://localhost:3003/api/banking/transactions/demo-user-123?limit=3` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3003/api/banking/transact…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/broker/alpaca/account (services/dashboard/dashboard-api-server.js:734)
`services/dashboard/dashboard-api-server.js:734` calls `GET http://localhost:3003/api/broker/alpaca/account` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/broker/alpaca/account` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/broker/test-connection/alpaca (services/dashboard/dashboard-api-server.js:744)
`services/dashboard/dashboard-api-server.js:744` calls `GET http://localhost:3003/api/broker/test-connection/alpaca` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/broker/test-connection/alp…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/risk/config (services/dashboard/server.js:317)
`services/dashboard/server.js:317` calls `GET http://localhost:3003/api/risk/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/risk/config` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3003/api/risk/portfolio (services/dashboard/server.js:297)
`services/dashboard/server.js:297` calls `GET http://localhost:3003/api/risk/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/risk/portfolio` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/automation/status (tests/legacy/test-frontend-fixes.js:85)
`tests/legacy/test-frontend-fixes.js:85` calls `GET http://localhost:3004/api/automation/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/api/automation/status` If this points at an extern…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/automation/status (tests/legacy/test-real-market-data.js:52)
`tests/legacy/test-real-market-data.js:52` calls `GET http://localhost:3004/api/automation/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/api/automation/status` If this points at an exte…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/automation/strategies/performance (tests/legacy/test-frontend-fixes.js:61)
`tests/legacy/test-frontend-fixes.js:61` calls `GET http://localhost:3004/api/automation/strategies/performance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/api/automation/strategies/performa…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/banking/countries (tests/legacy/test-banking-integration.js:65)
`tests/legacy/test-banking-integration.js:65` calls `GET http://localhost:3004/api/banking/countries` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/api/banking/countries` If this points at an e…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/banking/exchange-rates (tests/legacy/test-banking-integration.js:72)
`tests/legacy/test-banking-integration.js:72` calls `GET http://localhost:3004/api/banking/exchange-rates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/api/banking/exchange-rates` If this poin…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/performance/overall (services/dashboard/server.js:387)
`services/dashboard/server.js:387` calls `GET http://localhost:3004/api/performance/overall` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/performance/overall` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/signals/recent?limit=20 (services/dashboard/server.js:407)
`services/dashboard/server.js:407` calls `GET http://localhost:3004/api/signals/recent?limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/signals/recent` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/strategies (services/dashboard/server.js:355)
`services/dashboard/server.js:355` calls `GET http://localhost:3004/api/strategies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/api/strategies/${strategyName} (services/dashboard/server.js:963)
`services/dashboard/server.js:963` calls `GET http://localhost:3004/api/strategies/${strategyName}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies/<p>` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3004/health (tests/legacy/test-real-market-data.js:49)
`tests/legacy/test-real-market-data.js:49` calls `GET http://localhost:3004/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:3004/health` If this points at an external API, prefix it with `http…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3005/api/trading/positions (services/dashboard/server.js:721)
`services/dashboard/server.js:721` calls `GET http://localhost:3005/api/trading/positions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3005/api/trading/positions` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3005/api/trading/status (services/dashboard/server.js:667)
`services/dashboard/server.js:667` calls `GET http://localhost:3005/api/trading/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3005/api/trading/status` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3006/api/gdpr/status (services/dashboard/server.js:770)
`services/dashboard/server.js:770` calls `GET http://localhost:3006/api/gdpr/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3006/api/gdpr/status` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3007/api/aml/dashboard (services/dashboard/server.js:792)
`services/dashboard/server.js:792` calls `GET http://localhost:3007/api/aml/dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3007/api/aml/dashboard` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3008/api/reports (services/dashboard/server.js:823)
`services/dashboard/server.js:823` calls `GET http://localhost:3008/api/reports` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3008/api/reports` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3010/api/dashboard (tests/legacy/test-dashboard-data.js:12)
`tests/legacy/test-dashboard-data.js:12` calls `GET http://localhost:3010/api/dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3010/api/dashboard` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080/api/risk/portfolio (tests/legacy/test-dashboard-data.js:55)
`tests/legacy/test-dashboard-data.js:55` calls `GET http://localhost:8080/api/risk/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080/api/risk/portfolio` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080/api/strategies (tests/legacy/test-dashboard-data.js:42)
`tests/legacy/test-dashboard-data.js:42` calls `GET http://localhost:8080/api/strategies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080/api/strategies` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080/api/trading/status (tests/legacy/test-dashboard-data.js:29)
`tests/legacy/test-dashboard-data.js:29` calls `GET http://localhost:8080/api/trading/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080/api/trading/status` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://finnhub.io/api/v1/quote (docs/archive/legacy-dir/enhanced-market-data-server.js:63)
`docs/archive/legacy-dir/enhanced-market-data-server.js:63` calls `GET https://finnhub.io/api/v1/quote` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/finnhub.io/api/v1/quote` If this points at an external AP…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://futures.kraken.com/derivatives/api/v3/tickers (clients/bot-dashboard/unified-crypto-bot.js:5001)
`clients/bot-dashboard/unified-crypto-bot.js:5001` calls `GET https://futures.kraken.com/derivatives/api/v3/tickers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/futures.kraken.com/derivatives/api/v3/ticker…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://futures.kraken.com/derivatives/api/v3/tickers (deploy/crypto-bot/unified-crypto-bot.js:5001)
`deploy/crypto-bot/unified-crypto-bot.js:5001` calls `GET https://futures.kraken.com/derivatives/api/v3/tickers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/futures.kraken.com/derivatives/api/v3/tickers` I…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.alphavantage.co/query (docs/archive/legacy-dir/enhanced-market-data-server.js:246)
`docs/archive/legacy-dir/enhanced-market-data-server.js:246` calls `GET https://www.alphavantage.co/query` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/www.alphavantage.co/query` If this points at an extern…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3002/orders (docs/archive/legacy-dir/trading-server.js:107)
`docs/archive/legacy-dir/trading-server.js:107` calls `POST http://localhost:3002/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3002/orders (web-app/src/components/TradingInterface.js:99)
`web-app/src/components/TradingInterface.js:99` calls `POST http://localhost:3002/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3002/orders` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3003/api/broker/connect-alpaca (services/dashboard/dashboard-api-server.js:720)
`services/dashboard/dashboard-api-server.js:720` calls `POST http://localhost:3003/api/broker/connect-alpaca` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/broker/connect-alpaca` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3003/api/broker/test-alpaca (services/dashboard/dashboard-api-server.js:706)
`services/dashboard/dashboard-api-server.js:706` calls `POST http://localhost:3003/api/broker/test-alpaca` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/broker/test-alpaca` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3003/api/risk/emergency-stop (services/dashboard/server.js:337)
`services/dashboard/server.js:337` calls `POST http://localhost:3003/api/risk/emergency-stop` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3003/api/risk/emergency-stop` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3004/api/strategies/${strategyName}/activate (services/dashboard/server.js:438)
`services/dashboard/server.js:438` calls `POST http://localhost:3004/api/strategies/${strategyName}/activate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies/<p>/activate` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3004/api/strategies/${strategyName}/configure (services/dashboard/server.js:1012)
`services/dashboard/server.js:1012` calls `POST http://localhost:3004/api/strategies/${strategyName}/configure` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies/<p>/configure` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3004/api/strategies/${strategyName}/deactivate (services/dashboard/server.js:455)
`services/dashboard/server.js:455` calls `POST http://localhost:3004/api/strategies/${strategyName}/deactivate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies/<p>/deactivate` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3004/api/strategies/${strategyName}/test (services/dashboard/server.js:1040)
`services/dashboard/server.js:1040` calls `POST http://localhost:3004/api/strategies/${strategyName}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3004/api/strategies/<p>/test` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3005/api/trading/manual-order (services/dashboard/server.js:751)
`services/dashboard/server.js:751` calls `POST http://localhost:3005/api/trading/manual-order` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3005/api/trading/manual-order` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3005/api/trading/start (services/dashboard/server.js:689)
`services/dashboard/server.js:689` calls `POST http://localhost:3005/api/trading/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3005/api/trading/start` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3005/api/trading/stop (services/dashboard/server.js:705)
`services/dashboard/server.js:705` calls `POST http://localhost:3005/api/trading/stop` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3005/api/trading/stop` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3008/api/reports/generate (services/dashboard/server.js:850)
`services/dashboard/server.js:850` calls `POST http://localhost:3008/api/reports/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3008/api/reports/generate` If this points at an external API,…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (clients/bot-dashboard/unified-trading-bot.js:5941)
`clients/bot-dashboard/unified-trading-bot.js:5941` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this p…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (clients/bot-dashboard/unified-trading-bot.js:5981)
`clients/bot-dashboard/unified-trading-bot.js:5981` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this p…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (deploy/stock-bot/unified-trading-bot.js:5941)
`deploy/stock-bot/unified-trading-bot.js:5941` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (deploy/stock-bot/unified-trading-bot.js:5981)
`deploy/stock-bot/unified-trading-bot.js:5981` calls `POST https://api.telegram.org/bot${token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${sid}/Messages.json (clients/bot-dashboard/unified-trading-bot.js:5955)
`clients/bot-dashboard/unified-trading-bot.js:5955` calls `POST https://api.twilio.com/2010-04-01/Accounts/${sid}/Messages.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/accoun…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${sid}/Messages.json (deploy/stock-bot/unified-trading-bot.js:5955)
`deploy/stock-bot/unified-trading-bot.js:5955` calls `POST https://api.twilio.com/2010-04-01/Accounts/${sid}/Messages.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/accounts/<p…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (clients/bot-dashboard/unified-crypto-bot.js:4718)
`clients/bot-dashboard/unified-crypto-bot.js:4718` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an e…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (clients/bot-dashboard/unified-forex-bot.js:345)
`clients/bot-dashboard/unified-forex-bot.js:345` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an ext…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (clients/bot-dashboard/unified-trading-bot.js:121)
`clients/bot-dashboard/unified-trading-bot.js:121` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an e…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (deploy/crypto-bot/unified-crypto-bot.js:4718)
`deploy/crypto-bot/unified-crypto-bot.js:4718` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an exter…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (deploy/forex-bot/unified-forex-bot.js:345)
`deploy/forex-bot/unified-forex-bot.js:345` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an external…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://backboard.railway.app/graphql/v2 (deploy/stock-bot/unified-trading-bot.js:121)
`deploy/stock-bot/unified-trading-bot.js:121` calls `POST https://backboard.railway.app/graphql/v2` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/backboard.railway.app/graphql/v2` If this points at an extern…
Dangling fetchAxios
high System graph security auth conf 1.00 FastAPI DELETE `revoke_key` without auth dependency — services/strategy-engine/public_api_routes.py:227
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/public_api_routes.py:227 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_backfill_json` without auth dependency — services/strategy-engine/strategy_bridge.py:1408
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1408 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_backfill` without auth dependency — services/strategy-engine/strategy_bridge.py:1389
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1389 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_daily_training` without auth dependency — services/strategy-engine/strategy_bridge.py:1422
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1422 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_evaluate` without auth dependency — services/strategy-engine/strategy_bridge.py:1011
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1011 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_execution` without auth dependency — services/strategy-engine/strategy_bridge.py:1118
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1118 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_kill` without auth dependency — services/strategy-engine/strategy_bridge.py:1223
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1223 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_resume` without auth dependency — services/strategy-engine/strategy_bridge.py:1229
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1229 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_trade_outcome` without auth dependency — services/strategy-engine/strategy_bridge.py:1072
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1072 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ai_evaluate` without auth dependency — services/strategy-engine/strategy_bridge.py:975
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:975 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze_pair` without auth dependency — services/strategy-engine/strategy_bridge.py:932
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:932 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bandit_context_detail` without auth dependency — services/strategy-engine/strategy_bridge.py:1304
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1304 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bandit_select` without auth dependency — services/strategy-engine/strategy_bridge.py:1282
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1282 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bandit_sync_db` without auth dependency — services/strategy-engine/strategy_bridge.py:1332
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1332 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bandit_train` without auth dependency — services/strategy-engine/strategy_bridge.py:1338
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1338 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_portfolio_risk` without auth dependency — services/strategy-engine/strategy_bridge.py:1535
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1535 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_checkout` without auth dependency — services/strategy-engine/stripe_billing.py:87
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/stripe_billing.py:87 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_key` without auth dependency — services/strategy-engine/public_api_routes.py:194
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/public_api_routes.py:194 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_portal_session` without auth dependency — services/strategy-engine/stripe_billing.py:126
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/stripe_billing.py:126 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `evaluate_signal` without auth dependency — services/strategy-engine/public_api_routes.py:93
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/public_api_routes.py:93 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `get_ensemble_signal` without auth dependency — services/strategy-engine/strategy_bridge.py:309
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:309 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ml_features` without auth dependency — services/strategy-engine/strategy_bridge.py:597
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:597 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ml_fit` without auth dependency — services/strategy-engine/strategy_bridge.py:880
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:880 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ml_regime` without auth dependency — services/strategy-engine/strategy_bridge.py:486
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:486 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ml_score` without auth dependency — services/strategy-engine/strategy_bridge.py:830
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:830 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — services/strategy-engine/stripe_billing.py:166
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/stripe_billing.py:166 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_rankings` without auth dependency — services/strategy-engine/strategy_bridge.py:1475
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/strategy-engine/strategy_bridge.py:1475 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 Flask mutation route `activate_strategy` without `@login_required` — services/strategy-engine/api_server.py:103
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:103 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `deactivate_strategy` without `@login_required` — services/strategy-engine/api_server.py:119
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:119 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `generate_ensemble_signal` without `@login_required` — services/strategy-engine/api_server.py:359
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:359 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `generate_signals` without `@login_required` — services/strategy-engine/api_server.py:155
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:155 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `import_configuration` without `@login_required` — services/strategy-engine/api_server.py:271
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:271 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `update_ensemble_performance` without `@login_required` — services/strategy-engine/api_server.py:474
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:474 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `update_market_data` without `@login_required` — services/strategy-engine/api_server.py:290
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:290 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `update_strategy_parameters` without `@login_required` — services/strategy-engine/api_server.py:135
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:135 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `update_strategy_weight` without `@login_required` — services/strategy-engine/api_server.py:452
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
services/strategy-engine/api_server.py:452 securityAuth flask unauth route
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — services/dashboard/server.js:1012
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/commands/health.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/commands/health.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/status.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/commands/status.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, 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 Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: clients/web-app/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 2 occurrences Frontend route `/pricing` has no Link/navigate to it — clients/bot-dashboard/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
2 occurrences
repo-level (2 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
gitleaks/gitleaks-action@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/security.yml:82 CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in clients/bot-dashboard/crypto-bot-stub.js:13
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
clients/bot-dashboard/crypto-bot-stub.js:13 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in clients/bot-dashboard/gap-fade-bot.js:35
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
clients/bot-dashboard/gap-fade-bot.js:35 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in clients/bot-dashboard/high-volume-breakout-bot.js:37
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
clients/bot-dashboard/high-volume-breakout-bot.js:37 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in clients/bot-dashboard/orb-trading-bot.js:36
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
clients/bot-dashboard/orb-trading-bot.js:36 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in clients/bot-dashboard/unified-trading-bot-improved.js:20
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
clients/bot-dashboard/unified-trading-bot-improved.js:20 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/automation-server.js:20
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/automation-server.js:20 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/enhanced-integration-server.js:57
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/enhanced-integration-server.js:57 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/enhanced-market-data-server.js:18
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/enhanced-market-data-server.js:18 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/mock-market-data-server.js:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/mock-market-data-server.js:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/platform-demo.js:316
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/platform-demo.js:316 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/trading-server.js:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/trading-server.js:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in docs/archive/legacy-dir/trading-service.js:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
docs/archive/legacy-dir/trading-service.js:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/dashboard/dashboard-api-server.js:12
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/dashboard/dashboard-api-server.js:12 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/dashboard/server.js:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/dashboard/server.js:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/strategy-engine/strategy_bridge.py:265
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/strategy-engine/strategy_bridge.py:265 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/legacy-dir/automation-dashboard.html:378
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/legacy-dir/automation-dashboard.html:378 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/legacy-dir/enhanced-trading-dashboard.html:522
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/legacy-dir/enhanced-trading-dashboard.html:522 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/legacy-dir/enterprise-dashboard.html:1055
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/legacy-dir/enterprise-dashboard.html:1055 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/archive/legacy-dir/REAL_POSITIONS_DASHBOARD.html:256
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/archive/legacy-dir/REAL_POSITIONS_DASHBOARD.html:256 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in clients/bot-dashboard/src/pages/LoginPage.tsx:41
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
clients/bot-dashboard/src/pages/LoginPage.tsx:41 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in clients/bot-dashboard/src/services/api.ts:96
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
clients/bot-dashboard/src/services/api.ts:96 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in clients/desktop-app/src/renderer/store/slices/authSlice.ts:47
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
clients/desktop-app/src/renderer/store/slices/authSlice.ts:47 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — data-infrastructure/orchestration/airflow/dags/market_data_pipeline.py:75
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 113 placeholder/mock markers across 29 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 141 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ACTIVE_ACCOUNT`, `ALLOWED_ORIGINS`, `ALPACA_API_KEY`, `ALPACA_BASE_URL`, `ALPACA_PAPER`, `ALPACA_SECRET_KEY`, `ALPHA_VANTAGE_API_KEY`, `ANALYZE` + 133 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 2487 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 cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/cache@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 5 locations
.github/workflows/ci.yml:29, 58, 81 (3 hits)
.github/workflows/deploy.yml:47
.github/workflows/nightly-strategy-health.yml:120
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'debug_true' in services/strategy-engine/api_server.py:500
Found a known-risky pattern (debug_true). Review and replace if possible.
services/strategy-engine/api_server.py:500 Debug true
low System graph security security conf 1.00 Insecure pattern 'debug_true' in services/strategy-engine/README.md:335
Found a known-risky pattern (debug_true). Review and replace if possible.
services/strategy-engine/README.md:335 Debug true
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 9 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: .claude/hooks/trading-redteam-post.py:main, .claude/hooks/deploy-guardian-pre.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
9 occurrences
repo-level (9 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: services/strategy-engine/agents/macro_agent.py:get_stats, services/strategy-engine/agents/sentiment_agent.py:get_stats, services/strategy-engine/agents/institutional_agent.py:get_stats This is *the* AI-coder failure mode (4× more duplication in vibe-…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: services/strategy-engine/strategies.py:generate_signal, services/strategy-engine/strategies.py:generate_signal, services/strategy-engine/strategies.py:generate_signal, services/strategy-engine/strategies.py:generate_signal This is *the* AI-coder fail…
3 occurrences
repo-level (3 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: data-infrastructure/processing/flink/stream-processors/real_time_analytics_processor.py:process_element, data-infrastructure/processing/flink/stream-processors/real_time_analytics_processor.py:process, data-infrastructure/processing/flink/stream-proce…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 9 places
Functions with the same first-5-line body hash: data-infrastructure/storage/timeseries/influxdb/schemas/measurement_schemas.py:to_influx_point, data-infrastructure/storage/timeseries/influxdb/schemas/measurement_schemas.py:to_influx_point, data-infrastructure/storage/timeseries/influxdb/schemas/mea…
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: clients/desktop-app/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.
clients/desktop-app/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: clients/pro-terminal/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.
clients/pro-terminal/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: clients/react-dashboard/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.
clients/react-dashboard/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: clients/web-app/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.
clients/web-app/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: deploy/crypto-bot/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.
deploy/crypto-bot/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: deploy/dashboard/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.
deploy/dashboard/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: deploy/forex-bot/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.
deploy/forex-bot/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: deploy/stock-bot/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.
deploy/stock-bot/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: 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.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: sdks/typescript/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.
sdks/typescript/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: services/signals/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.
services/signals/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: shared/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.
shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: src/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.
src/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `errorOnDeprecated` in jest.config.js:117
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 `logistic_v1` in services/strategy-engine/strategy_bridge.py:874
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: calculate_parkinson_volatility
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/VolatilityArbitrageStrategy.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: check_exit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/PairsTradingStrategy.py:355
low System graph software Dead code conf 1.00 Possibly dead Python function: forecast
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/ou_estimator.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: optimal_entry_zscore
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/ou_estimator.py:189
low System graph software Dead code conf 1.00 Possibly dead Python function: print_market_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data-infrastructure/streaming/kafka/consumers/market-data-consumer.py:353
low System graph software Dead code conf 1.00 Possibly dead Python function: process_element
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data-infrastructure/processing/flink/stream-processors/real_time_analytics_processor.py:151
low System graph software Dead code conf 1.00 Possibly dead Python function: record_error
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/agents/safety.py:69
low System graph software Dead code conf 1.00 Possibly dead Python function: remove_strategy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/ensemble_manager.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: remove_strategy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/strategy_manager.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_monthly_counters
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/public_api.py:274
low System graph software Dead code conf 1.00 Possibly dead Python function: save_to_db
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/strategy-engine/agents/autopsy_agent.py:583
low System graph software Dead code conf 1.00 Possibly dead Python function: setup_complete_schema
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data-infrastructure/storage/timeseries/influxdb/schemas/time_series_setup.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: to_influx_point
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data-infrastructure/storage/timeseries/influxdb/schemas/measurement_schemas.py:233
low System graph software Dead code conf 1.00 Possibly dead Python function: unregister_callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data-infrastructure/streaming/kafka/consumers/market-data-consumer.py:196
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/crypto-bot-stub.js:74
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/gap-fade-bot.js:86
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/high-volume-breakout-bot.js:107
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/orb-trading-bot.js:97
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/shared/auth.js:210
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/src/pages/DocsPage.tsx:601
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/unified-crypto-bot.js:47
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/unified-forex-bot.js:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/unified-trading-bot-improved.js:310
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/bot-dashboard/unified-trading-bot.js:53
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/main/updater.ts:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/App.tsx:28
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/components/Native/DesktopTradingWorkspace.tsx:158
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/pages/LoginPage.tsx:48
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/pages/RegisterPage.tsx:120
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/pages/TradingPage.tsx:134
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — clients/desktop-app/src/renderer/services/api.ts:233
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — demo/src/UltraEfficientTradingDemo.js:57
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/crypto-bot/shared/auth.js:210
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/crypto-bot/signals/schema.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/crypto-bot/unified-crypto-bot.js:47
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/dashboard/server.js:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/forex-bot/shared/auth.js:210
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/forex-bot/signals/schema.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/forex-bot/unified-forex-bot.js:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/shared/telegram-alerts.js:27
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/stock-bot/shared/auth.js:210
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/stock-bot/signals/schema.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — deploy/stock-bot/unified-trading-bot.js:53
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/automation-server.js:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/check-orders.js:26
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/enhanced-integration-server.js:48
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/enhanced-market-data-server.js:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/mock-market-data-server.js:211
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/platform-demo.js:350
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/simple-status.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/status-dashboard.js:85
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/track-trades.js:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/trading-server.js:146
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/archive/legacy-dir/trading-service.js:343
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — infrastructure/memory/MemoryManager.js:44
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — infrastructure/notifications/telegram-alerts.js:27
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/analyze-committee-threshold.js:73
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/analyze-exit-by-confidence.js:60
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/crypto-edge-monitor.js:88
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/fix-pnl-pct.js:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/run-strategy-evidence.js:239
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — sdks/typescript/src/index.ts:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/backtesting-js/cli.js:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/backtesting-js/verify-migration.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/dashboard/dashboard-api-server.js:394
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/dashboard/index.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/dashboard/server.js:1145
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/market-archive/archiver.js:127
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/signals/backtest/kill-switch-oos.js:134
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/signals/backtest/qualifier-backtest.js:151
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/signals/edge-stats-coverage.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/signals/schema.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/strategy-engine/NexusAlpha.js:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/demo.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/libs/database/connection-pools.js:83
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/libs/database/migrations.js:94
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/libs/messaging/kafka-client.js:60
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/libs/messaging/redis-client.js:47
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — shared/test.js:2
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/NexusTradeSystemOrchestrator.js:85
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/test-orchestrator.js:63
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-banking-integration.js:4
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-complete-system.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-core-system.js:10
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-dashboard-data.js:7
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-enhanced-features.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-enhanced-frontend.js:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-exports-fix.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-frontend-fixes.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-immediate-next-steps.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-python-bridge.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/legacy/test-real-market-data.js:10
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/setup/jest.setup.js:306
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/strategy-tests.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/unit/technical-indicators.test.js:127
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/config/export
`services/strategy-engine/api_server.py` declares `ANY /api/config/export` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/config/import
`services/strategy-engine/api_server.py` declares `ANY /api/config/import` 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: ANY /api/ensemble/analytics
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/analytics` 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: ANY /api/ensemble/performance/update
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/performance/update` 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: ANY /api/ensemble/signal
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/signal` 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: ANY /api/ensemble/summary
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/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: ANY /api/ensemble/weights
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/weights` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/ensemble/weights/<strategy_name>
`services/strategy-engine/api_server.py` declares `ANY /api/ensemble/weights/<strategy_name>` 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: ANY /api/market-data/update
`services/strategy-engine/api_server.py` declares `ANY /api/market-data/update` 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: ANY /api/performance/<strategy_name>
`services/strategy-engine/api_server.py` declares `ANY /api/performance/<strategy_name>` 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: ANY /api/performance/overall
`services/strategy-engine/api_server.py` declares `ANY /api/performance/overall` 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: ANY /api/signals/generate
`services/strategy-engine/api_server.py` declares `ANY /api/signals/generate` 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: ANY /api/signals/mock
`services/strategy-engine/api_server.py` declares `ANY /api/signals/mock` 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: ANY /api/signals/recent
`services/strategy-engine/api_server.py` declares `ANY /api/signals/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: ANY /api/strategies
`services/strategy-engine/api_server.py` declares `ANY /api/strategies` 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: ANY /api/strategies/<strategy_name>
`services/strategy-engine/api_server.py` declares `ANY /api/strategies/<strategy_name>` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/strategies/<strategy_name>/activate
`services/strategy-engine/api_server.py` declares `ANY /api/strategies/<strategy_name>/activate` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/strategies/<strategy_name>/deactivate
`services/strategy-engine/api_server.py` declares `ANY /api/strategies/<strategy_name>/deactivate` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/strategies/<strategy_name>/parameters
`services/strategy-engine/api_server.py` declares `ANY /api/strategies/<strategy_name>/parameters` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /agent/bandit/stats
`services/strategy-engine/strategy_bridge.py` declares `GET /agent/bandit/stats` 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 /agent/debug-claude
`services/strategy-engine/strategy_bridge.py` declares `GET /agent/debug-claude` 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 /agent/decisions
`services/strategy-engine/strategy_bridge.py` declares `GET /agent/decisions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /agent/rankings
`services/strategy-engine/strategy_bridge.py` declares `GET /agent/rankings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint

Showing first 300 of 337. 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/ed213479-92b3-41fc-8366-aa563589ef7c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ed213479-92b3-41fc-8366-aa563589ef7c/

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.