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

Viniciusvile/Trading-ia

https://github.com/Viniciusvile/Trading-ia · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

203 raw signals (0 security + 203 graph)

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

Complete repo analysis

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

JSON
Combined
48.9
/100
Security checks
49
0 findings
System graph
49
88.9% cov · 203 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 82 Medium 27 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 203 Crowd 0 Layer: Frontend 35 Security 9 Cicd 1 Quality 26 Api 132
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 48.9/100 with 88.9% coverage. It contains 1068 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 203 findings — concentrated in api (132), frontend (35), quality (26). Risk profile is high: 0 critical, 82 high, 27 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 190 of 203 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.binance.com/api/v3/openOrders?${cQs}&signature=${cSig} (masterbot/bot.js:1264)
`masterbot/bot.js:1264` calls `DELETE https://api.binance.com/api/v3/openOrders?${cQs}&signature=${cSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/openorders` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.binance.com/api/v3/orderList?${qs}&signature=${sig} (dashboard/server.js:2904)
`dashboard/server.js:2904` calls `DELETE https://api.binance.com/api/v3/orderList?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/orderlist` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://${CDP_HOST}:${CDP_PORT}/json/activate/${target.id} (src/core/tab.js:100)
`src/core/tab.js:100` calls `GET http://${CDP_HOST}:${CDP_PORT}/json/activate/${target.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/<p>:/<p>/json/activate/<p>` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://${CDP_HOST}:${CDP_PORT}/json/list (src/connection.js:93)
`src/connection.js:93` calls `GET http://${CDP_HOST}:${CDP_PORT}/json/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/<p>:/<p>/json/list` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://${CDP_HOST}:${CDP_PORT}/json/list (src/core/tab.js:14)
`src/core/tab.js:14` calls `GET http://${CDP_HOST}:${CDP_PORT}/json/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/<p>:/<p>/json/list` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://${CDP_HOST}:${CDP_PORT}/json/version (src/connection.js:76)
`src/connection.js:76` calls `GET http://${CDP_HOST}:${CDP_PORT}/json/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/<p>:/<p>/json/version` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:9222/json/list (scripts/pine_pull.js:6)
`scripts/pine_pull.js:6` calls `GET http://localhost:9222/json/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:9222/json/list` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:9222/json/list (scripts/pine_push.js:9)
`scripts/pine_push.js:9` calls `GET http://localhost:9222/json/list` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:9222/json/list` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qsAcc}&signature=${sigAcc} (dashboard/server.js:2919)
`dashboard/server.js:2919` calls `GET https://api.binance.com/api/v3/account?${qsAcc}&signature=${sigAcc}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qsA}&signature=${sigA} (dashboard/server.js:3036)
`dashboard/server.js:3036` calls `GET https://api.binance.com/api/v3/account?${qsA}&signature=${sigA}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qsS}&signature=${sigS} (dashboard/server.js:3235)
`dashboard/server.js:3235` calls `GET https://api.binance.com/api/v3/account?${qsS}&signature=${sigS}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qsS}&signature=${sigS} (masterbot/bot.js:819)
`masterbot/bot.js:819` calls `GET https://api.binance.com/api/v3/account?${qsS}&signature=${sigS}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qs}&signature=${sig} (dashboard/server.js:2750)
`dashboard/server.js:2750` calls `GET https://api.binance.com/api/v3/account?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${qs}&signature=${sig} (dashboard/server.js:3286)
`dashboard/server.js:3286` calls `GET https://api.binance.com/api/v3/account?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/account?${sQs}&signature=${sSig} (masterbot/bot.js:1363)
`masterbot/bot.js:1363` calls `GET https://api.binance.com/api/v3/account?${sQs}&signature=${sSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/account` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/exchangeInfo?symbol=${pos.symbol} (dashboard/server.js:3042)
`dashboard/server.js:3042` calls `GET https://api.binance.com/api/v3/exchangeInfo?symbol=${pos.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/exchangeinfo` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/exchangeInfo?symbol=${symbol} (dashboard/server.js:2002)
`dashboard/server.js:2002` calls `GET https://api.binance.com/api/v3/exchangeInfo?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/exchangeinfo` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/exchangeInfo?symbol=${symbol} (dashboard/server.js:2800)
`dashboard/server.js:2800` calls `GET https://api.binance.com/api/v3/exchangeInfo?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/exchangeinfo` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/klines?symbol=${chartSymbol}&interval=1h&limit=168 (trading-saas/frontend/src/app/page.tsx:75)
`trading-saas/frontend/src/app/page.tsx:75` calls `GET https://api.binance.com/api/v3/klines?symbol=${chartSymbol}&interval=1h&limit=168` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/order?${oQs}&signature=${oSig} (dashboard/server.js:2587)
`dashboard/server.js:2587` calls `GET https://api.binance.com/api/v3/order?${oQs}&signature=${oSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/order` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/order?${qs}&signature=${sig} (dashboard/server.js:2639)
`dashboard/server.js:2639` calls `GET https://api.binance.com/api/v3/order?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/order` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/orderList?${qs}&signature=${sig} (dashboard/server.js:2561)
`dashboard/server.js:2561` calls `GET https://api.binance.com/api/v3/orderList?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/orderlist` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/24hr?symbol=${symbol} (dashboard/server.js:505)
`dashboard/server.js:505` calls `GET https://api.binance.com/api/v3/ticker/24hr?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/24hr` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price (trading-saas/frontend/src/app/posicoes/page.tsx:111)
`trading-saas/frontend/src/app/posicoes/page.tsx:111` calls `GET https://api.binance.com/api/v3/ticker/price` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT (dashboard/server.js:2726)
`dashboard/server.js:2726` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT (dashboard/server.js:3246)
`dashboard/server.js:3246` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT (dashboard/server.js:3301)
`dashboard/server.js:3301` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${b.asset}USDT` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${pos.symbol} (dashboard/server.js:2616)
`dashboard/server.js:2616` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${pos.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${pos.symbol} (dashboard/server.js:3046)
`dashboard/server.js:3046` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${pos.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${req.params.symbol} (dashboard/server.js:3322)
`dashboard/server.js:3322` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${req.params.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol} (dashboard/server.js:2765)
`dashboard/server.js:2765` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol} (dashboard/server.js:3370)
`dashboard/server.js:3370` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol} (masterbot/bot.js:1137)
`masterbot/bot.js:1137` calls `GET https://api.binance.com/api/v3/ticker/price?symbol=${symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/ticker/price` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2558)
`dashboard/server.js:2558` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2584)
`dashboard/server.js:2584` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2636)
`dashboard/server.js:2636` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2747)
`dashboard/server.js:2747` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2900)
`dashboard/server.js:2900` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2915)
`dashboard/server.js:2915` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:2929)
`dashboard/server.js:2929` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:3033)
`dashboard/server.js:3033` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:3069)
`dashboard/server.js:3069` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:3232)
`dashboard/server.js:3232` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:3282)
`dashboard/server.js:3282` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (dashboard/server.js:3375)
`dashboard/server.js:3375` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (masterbot/bot.js:1113)
`masterbot/bot.js:1113` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (masterbot/bot.js:1192)
`masterbot/bot.js:1192` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (masterbot/bot.js:816)
`masterbot/bot.js:816` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.binance.com/api/v3/time (masterbot/bot.js:871)
`masterbot/bot.js:871` calls `GET https://api.binance.com/api/v3/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/time` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://economia.awesomeapi.com.br/json/last/USD-BRL (dashboard/server.js:3310)
`dashboard/server.js:3310` calls `GET https://economia.awesomeapi.com.br/json/last/USD-BRL` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/economia.awesomeapi.com.br/json/last/usd-brl` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/exchangeInfo?symbol=${pos.symbol} (dashboard/server.js:2869)
`dashboard/server.js:2869` calls `GET https://fapi.binance.com/fapi/v1/exchangeInfo?symbol=${pos.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/exchangeinfo` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/exchangeInfo?symbol=${pos.symbol} (dashboard/server.js:2986)
`dashboard/server.js:2986` calls `GET https://fapi.binance.com/fapi/v1/exchangeInfo?symbol=${pos.symbol}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/exchangeinfo` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/openOrders?${oQs}&signature=${oSig} (masterbot/bot.js:1328)
`masterbot/bot.js:1328` calls `GET https://fapi.binance.com/fapi/v1/openOrders?${oQs}&signature=${oSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/openorders` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/time (dashboard/server.js:2882)
`dashboard/server.js:2882` calls `GET https://fapi.binance.com/fapi/v1/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/time` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/time (dashboard/server.js:3256)
`dashboard/server.js:3256` calls `GET https://fapi.binance.com/fapi/v1/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/time` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v1/time (masterbot/bot.js:828)
`masterbot/bot.js:828` calls `GET https://fapi.binance.com/fapi/v1/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/time` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v2/account?${qsF}&signature=${sigF} (dashboard/server.js:3259)
`dashboard/server.js:3259` calls `GET https://fapi.binance.com/fapi/v2/account?${qsF}&signature=${sigF}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v2/account` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v2/account?${qsF}&signature=${sigF} (masterbot/bot.js:831)
`masterbot/bot.js:831` calls `GET https://fapi.binance.com/fapi/v2/account?${qsF}&signature=${sigF}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v2/account` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://fapi.binance.com/fapi/v2/positionRisk?${qs}&signature=${sig} (masterbot/bot.js:1304)
`masterbot/bot.js:1304` calls `GET https://fapi.binance.com/fapi/v2/positionRisk?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v2/positionrisk` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pine-facade.tradingview.com/pine-facade/list/?filter=saved (src/core/pine.js:559)
`src/core/pine.js:559` calls `GET https://pine-facade.tradingview.com/pine-facade/list/?filter=saved` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pine-facade.tradingview.com/pine-facade/list` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pine-facade.tradingview.com/pine-facade/list/?filter=saved (src/core/pine.js:606)
`src/core/pine.js:606` calls `GET https://pine-facade.tradingview.com/pine-facade/list/?filter=saved` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pine-facade.tradingview.com/pine-facade/list` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://pricealerts.tradingview.com/list_alerts (src/core/alerts.js:78)
`src/core/alerts.js:78` calls `GET https://pricealerts.tradingview.com/list_alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/pricealerts.tradingview.com/list_alerts` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://symbol-search.tradingview.com/symbol_search/v3/?${params} (src/core/chart.js:209)
`src/core/chart.js:209` calls `GET https://symbol-search.tradingview.com/symbol_search/v3/?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/symbol-search.tradingview.com/symbol_search/v3` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${process.env.PORT || 3334}/api/alerts (masterbot/bot.js:1933)
`masterbot/bot.js:1933` calls `POST http://localhost:${process.env.PORT || 3334}/api/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:/<p>/api/alerts` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:${process.env.PORT || 3334}/api/symbol (masterbot/bot.js:1619)
`masterbot/bot.js:1619` calls `POST http://localhost:${process.env.PORT || 3334}/api/symbol` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:/<p>/api/symbol` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3333/api/symbol (masterbot/bot.js:1918)
`masterbot/bot.js:1918` calls `POST http://localhost:3333/api/symbol` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3333/api/symbol` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3333/api/timeframe (masterbot/bot.js:1923)
`masterbot/bot.js:1923` calls `POST http://localhost:3333/api/timeframe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3333/api/timeframe` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.binance.com/api/v3/order/oco?${qs}&signature=${sig} (dashboard/server.js:3076)
`dashboard/server.js:3076` calls `POST https://api.binance.com/api/v3/order/oco?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/order/oco` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.binance.com/api/v3/order?${qs}&signature=${sig} (dashboard/server.js:2933)
`dashboard/server.js:2933` calls `POST https://api.binance.com/api/v3/order?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/order` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.binance.com/api/v3/order?${qs}&signature=${sig} (dashboard/server.js:3379)
`dashboard/server.js:3379` calls `POST https://api.binance.com/api/v3/order?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.binance.com/api/v3/order` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${token}/sendMessage (micro-scalper.js:78)
`micro-scalper.js:78` 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: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://fapi.binance.com/fapi/v1/order?${qsTP}&signature=${sigTP} (dashboard/server.js:3017)
`dashboard/server.js:3017` calls `POST https://fapi.binance.com/fapi/v1/order?${qsTP}&signature=${sigTP}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/order` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://fapi.binance.com/fapi/v1/order?${qs}&signature=${sig} (dashboard/server.js:2887)
`dashboard/server.js:2887` calls `POST https://fapi.binance.com/fapi/v1/order?${qs}&signature=${sig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/order` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://fapi.binance.com/fapi/v1/order?${slQuery}&signature=${slSig} (masterbot/bot.js:995)
`masterbot/bot.js:995` calls `POST https://fapi.binance.com/fapi/v1/order?${slQuery}&signature=${slSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/order` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://fapi.binance.com/fapi/v1/order?${tpQuery}&signature=${tpSig} (masterbot/bot.js:1013)
`masterbot/bot.js:1013` calls `POST https://fapi.binance.com/fapi/v1/order?${tpQuery}&signature=${tpSig}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/fapi.binance.com/fapi/v1/order` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${model}:generateContent?key=${apiKey} (dashboard/server.js:1484)
`dashboard/server.js:1484` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${model}:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/generativelanguage.googlea…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash:generateContent?key=${apiKey} (src/ai/reviewer.js:46)
`src/ai/reviewer.js:46` calls `POST https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/generativelanguage.go…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000 (src/core/pine.js:203)
`src/core/pine.js:203` calls `POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000 (tests/e2e.test.js:909)
`tests/e2e.test.js:909` calls `POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000 (tests/pine_analyze.test.js:252)
`tests/pine_analyze.test.js:252` calls `POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000 (tests/pine_analyze.test.js:278)
`tests/pine_analyze.test.js:278` calls `POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000 (tests/pine_analyze.test.js:307)
`tests/pine_analyze.test.js:307` calls `POST https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching:…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — trading-saas/frontend/src/app/login/page.tsx:206
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — adaptive-bot/bot.js:28
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/server.js:1653
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — masterbot/bot.js:149
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — masterbot/cleanup.js:24
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — masterbot/range-backtest.js:186
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/pine_pull.js:6
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/pine_push.js:9
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/connection.js:93
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/chart.js:209
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/pine.js:203
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/tab.js:14
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — trading-saas/frontend/src/lib/api.ts:143
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — trading-saas/frontend/src/lib/apiV2.ts:15
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in dashboard/server-optimized.js:8
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
dashboard/server-optimized.js:8 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in trading-saas/frontend/src/app/login/page.tsx:206
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
trading-saas/frontend/src/app/login/page.tsx:206 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/index.html:1641
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/index.html:1641 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in trading-saas/frontend/src/components/TradingViewWidget.tsx:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
trading-saas/frontend/src/components/TradingViewWidget.tsx:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in dashboard/index.html:4853
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
dashboard/index.html:4853 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in dashboard/index.html:2244
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
dashboard/index.html:2244 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in trading-saas/frontend/src/app/login/page.tsx:128
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
trading-saas/frontend/src/app/login/page.tsx:128 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in dashboard/server.js:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
dashboard/server.js:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/health.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/health.js:6 Node child process
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 25 placeholder/mock markers across 13 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 Debug conf 1.00 Debug logging residue appears in source files
Found 330 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Tests conf 1.00 Low test-to-source ratio
22 tests / 142 src (ratio 0.15).
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 — adaptive-bot/bot.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 — analyze_trades.js:18
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 — check-precision.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 — check_db.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 — dashboard/server.js:224
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 — fix-sol.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 — masterbot/bot.js:65
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 — masterbot/cleanup.js:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — masterbot/db.js:194
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 — masterbot/migrate-to-postgres.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 — masterbot/range-backtest.js:138
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 — masterbot/scratch/backtest-smoke.js:38
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 — masterbot/test_db.js:14
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 — micro-scalper.js:149
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 — scalper-run.js:189
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 — scratch_analyze_losses.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 — scratch_check_xrp.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 — scratch_market_check.js:9
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 — scratch_query_positions.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 — scripts/pine_pull.js:21
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/pine_push.js:23
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/cli/router.js:15
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/exchange/binance.js:157
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 — trading-saas/frontend/copy-standalone.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/alerts
`dashboard/server.js` declares `DELETE /api/alerts` 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: DELETE /api/journal/:id
`dashboard/server.js` declares `DELETE /api/journal/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/alerts
`dashboard/server.js` declares `GET /api/alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/me
`dashboard/server.js` declares `GET /api/auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/brief
`dashboard/server.js` declares `GET /api/brief` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`dashboard/server.js` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/indicators
`dashboard/server.js` declares `GET /api/indicators` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/journal
`dashboard/server.js` declares `GET /api/journal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/micro-scalper/config
`dashboard/server-optimized.js` declares `GET /api/micro-scalper/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/micro-scalper/signal
`dashboard/server-optimized.js` declares `GET /api/micro-scalper/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: GET /api/ohlcv
`dashboard/server.js` declares `GET /api/ohlcv` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/pine/console
`dashboard/server.js` declares `GET /api/pine/console` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/pine/errors
`dashboard/server.js` declares `GET /api/pine/errors` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/pine/list
`dashboard/server.js` declares `GET /api/pine/list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/pine/source
`dashboard/server.js` declares `GET /api/pine/source` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/quote
`dashboard/server.js` declares `GET /api/quote` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/replay/status
`dashboard/server.js` declares `GET /api/replay/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/screenshot-image
`dashboard/server.js` declares `GET /api/screenshot-image` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/screenshots/file/:name
`dashboard/server.js` declares `GET /api/screenshots/file/: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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/screenshots/list
`dashboard/server.js` declares `GET /api/screenshots/list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/state
`dashboard/server.js` declares `GET /api/state` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/strategies
`dashboard/server.js` declares `GET /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: GET /api/strategies/current
`dashboard/server.js` declares `GET /api/strategies/current` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/strategy
`dashboard/server.js` declares `GET /api/strategy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/strategy/equity
`dashboard/server.js` declares `GET /api/strategy/equity` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/strategy/trades
`dashboard/server.js` declares `GET /api/strategy/trades` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/symbol-search
`dashboard/server.js` declares `GET /api/symbol-search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/watchlist
`dashboard/server.js` declares `GET /api/watchlist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/micro-scalper/config
`dashboard/server-optimized.js` declares `PATCH /api/micro-scalper/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/alerts
`dashboard/server.js` declares `POST /api/alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/login
`dashboard/server.js` declares `POST /api/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/register
`dashboard/server.js` declares `POST /api/auth/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/chart/goto
`dashboard/server.js` declares `POST /api/chart/goto` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/journal
`dashboard/server.js` declares `POST /api/journal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/micro-scalper/sync-symbol
`dashboard/server.js` declares `POST /api/micro-scalper/sync-symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/micro-scalper/trade
`dashboard/server.js` declares `POST /api/micro-scalper/trade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/pine/compile
`dashboard/server.js` declares `POST /api/pine/compile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/pine/open
`dashboard/server.js` declares `POST /api/pine/open` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/pine/save
`dashboard/server.js` declares `POST /api/pine/save` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/pine/source
`dashboard/server.js` declares `POST /api/pine/source` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/replay/autoplay
`dashboard/server.js` declares `POST /api/replay/autoplay` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/replay/start
`dashboard/server.js` declares `POST /api/replay/start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/replay/step
`dashboard/server.js` declares `POST /api/replay/step` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/replay/stop
`dashboard/server.js` declares `POST /api/replay/stop` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/replay/trade
`dashboard/server.js` declares `POST /api/replay/trade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/scanner
`dashboard/server.js` declares `POST /api/scanner` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/screenshot
`dashboard/server.js` declares `POST /api/screenshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/symbol
`dashboard/server.js` declares `POST /api/symbol` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/timeframe
`dashboard/server.js` declares `POST /api/timeframe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/watchlist/add
`dashboard/server.js` declares `POST /api/watchlist/add` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: dashboard/server.js (3850 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: masterbot/bot.js (2257 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/e2e.test.js (1584 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: trading-saas/frontend/src/app/bots/page.tsx (1188 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/6c0028e8-e6a6-4bb2-bdc3-ce74f74d6e08/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6c0028e8-e6a6-4bb2-bdc3-ce74f74d6e08/

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.