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

TrendHunter/saibo-trader

https://github.com/TrendHunter/saibo-trader · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

62 raw signals (0 security + 62 graph)

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

Complete repo analysis

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

JSON
Combined
76.9
/100
Security checks
77
0 findings
System graph
77
100.0% cov · 54 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 1 Medium 8 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 54 Crowd 0 Layer: Software 21 Api 1 Frontend 4 Hardware 6 Cicd 1 Quality 21
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 76.9/100 with 100.0% coverage. It contains 771 nodes across 10 cross-layer flows, written primarily in mixed languages. Engine surfaced 62 findings — concentrated in quality (26), software (21), hardware (9). Risk profile is high: 0 critical, 1 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph quality Integrity conf 1.00 Blocking `requests.get(...)` inside `async def _bootstrap_price_from_rest` — reference_python_project/core/binance_ws.py:319
Sync I/O inside an async function blocks the event loop. While `requests.get(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_th…
reference_python_project/core/binance_ws.py:319 Sync io in asyncPerformance
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/risk/page.tsx:58
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — derive_keys.py:81
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
5 test file(s) for 86 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/components/dashboard/TradingPanels.tsx:88
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 34 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AUDIT_PATH`, `AUTH_PASSWORD`, `AUTH_USERNAME`, `BINANCE_RECONNECT_DELAY`, `BOT_API_URL`, `BOT_WS_URL`, `DH_TIMEOUT_SECONDS`, `EDGE_MIN_PRICE_MOVE` + 26 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 161 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 19
frontend/Dockerfile:1, 19 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 13, 34
reference_python_project/Dockerfile:13, 34 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 4, 33
Dockerfile:4, 33 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: test_sandbox.py:test_sandbox, test_auth.py:test_auth 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.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `exchange_v2` in live_preflight.py:29
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `py_clob_client_v2` in derive_and_update_keys.py:39
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 `py_clob_client_v2` in fetch_balance.py:64
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 `py_clob_client_v2` in test_auth.py:28
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `py_clob_client_v2` in test_sandbox.py:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: cancel_order
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/core/polymarket_client.py:1417
low System graph software Dead code conf 1.00 Possibly dead Python function: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/utils/retry.py:34
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:140
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:160
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_balances
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/core/polymarket_client.py:1474
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_pause
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/main.py:1525
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_reset_kill
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/main.py:1548
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_resume
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/main.py:1530
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/main.py:1535
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_stop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/main.py:1552
low System graph software Dead code conf 1.00 Possibly dead Python function: has_sufficient_liquidity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/core/polymarket_client.py:987
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:137
low System graph software Dead code conf 1.00 Possibly dead Python function: log_stderr
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:227
low System graph software Dead code conf 1.00 Possibly dead Python function: push_risk_alert
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/integration/openclaw.py:202
low System graph software Dead code conf 1.00 Possibly dead Python function: read_memory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/integration/openclaw.py:435
low System graph software Dead code conf 1.00 Possibly dead Python function: run_core
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:216
low System graph software Dead code conf 1.00 Possibly dead Python function: run_http_server
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboard_bridge.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: send_daily_halt_alert
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/integration/telegram.py:260
low System graph software Dead code conf 1.00 Possibly dead Python function: set_daily_starting_balance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/risk/risk_manager.py:480
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_memory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/integration/openclaw.py:418
low System graph software Dead code conf 1.00 Possibly dead Python function: unsubscribe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
reference_python_project/core/polymarket_ws.py:171
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/prisma/seed.ts:17
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 — frontend/src/app/api/live/route.ts: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 — frontend/src/lib/email.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: reference_python_project/core/polymarket_client.py (1484 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: reference_python_project/main.py (1823 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/c4f3d0c9-bc7b-4585-a5c1-adb2d6957d30/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c4f3d0c9-bc7b-4585-a5c1-adb2d6957d30/

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.