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

vincenzo000915-cmd/ai-quant

https://github.com/vincenzo000915-cmd/ai-quant · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

187 raw signals (3 security + 184 graph)

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

Complete repo analysis

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

JSON
Combined
51.2
/100
Security checks
51
3 findings
System graph
51
100.0% cov · 169 findings
Critical
2
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 2 High 14 Medium 26 Low 109 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 169 Crowd 0 Layer: Quality 63 Security 14 Software 29 Frontend 4 Network 1 Hardware 3 Cicd 1 Api 57
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 51.2/100 with 100.0% coverage. It contains 2316 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 184 findings — concentrated in quality (76), api (57), software (29). Risk profile is high: 1 critical, 13 high, 31 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: vincenzo000915-cmd/ai-quant
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
critical System graph security Secrets conf 1.00 Possible secret in scripts/migrate_phase_11_1.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/migrate_phase_11_1.py:7
high Security checks quality Practices conf 0.84 Foundry mined bad chains: vincenzo000915-cmd/ai-quant
Comment chain pattern product: bad_chains Repo: vincenzo000915-cmd/ai-quant Thread: vincenzo000915-cmd/ai-quant#1 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifa…
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/me/llm/${provider.id} (frontend/src/components/LlmBindingCard.js:137)
`frontend/src/components/LlmBindingCard.js:137` calls `DELETE /api/me/llm/${provider.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/llm/<p>` 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: DELETE /api/me/profit-target/${target.id} (frontend/src/components/ProfitTargetCard.js:98)
`frontend/src/components/ProfitTargetCard.js:98` calls `DELETE /api/me/profit-target/${target.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/profit-target/<p>` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/llm/${provider.id} (frontend/src/components/LlmBindingCard.js:124)
`frontend/src/components/LlmBindingCard.js:124` calls `PATCH /api/me/llm/${provider.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/llm/<p>` 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: POST /api/me/llm/${provider.id} (frontend/src/components/LlmBindingCard.js:93)
`frontend/src/components/LlmBindingCard.js:93` calls `POST /api/me/llm/${provider.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/llm/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/llm/${provider.id}/test (frontend/src/components/LlmBindingCard.js:114)
`frontend/src/components/LlmBindingCard.js:114` calls `POST /api/me/llm/${provider.id}/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/llm/<p>/test` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/profit-target/${t.id}/resume (frontend/src/components/ProfitTargetCard.js:130)
`frontend/src/components/ProfitTargetCard.js:130` calls `POST /api/me/profit-target/${t.id}/resume` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/me/profit-target/<p>/resume` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/strategies/${strategy.id}/explain (frontend/src/components/ExplainStrategyDialog.js:23)
`frontend/src/components/ExplainStrategyDialog.js:23` calls `POST /api/strategies/${strategy.id}/explain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/strategies/<p>/explain` If this points at an external API, pre…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'eval_used' in app/services/llm_prompts/strategy_synthesize.py:190
Found a known-risky pattern (eval_used). Review and replace if possible.
app/services/llm_prompts/strategy_synthesize.py:190 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in app/services/llm_prompts/strategy_synthesize_v2.py:728
Found a known-risky pattern (eval_used). Review and replace if possible.
app/services/llm_prompts/strategy_synthesize_v2.py:728 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in app/services/candidate_sandbox.py:102
Found a known-risky pattern (exec_used). Review and replace if possible.
app/services/candidate_sandbox.py:102 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in app/services/llm_prompts/strategy_synthesize.py:190
Found a known-risky pattern (exec_used). Review and replace if possible.
app/services/llm_prompts/strategy_synthesize.py:190 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in app/services/llm_prompts/strategy_synthesize_v2.py:728
Found a known-risky pattern (exec_used). Review and replace if possible.
app/services/llm_prompts/strategy_synthesize_v2.py:728 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in app/static/static/js/main.641d6522.js:2
Found a known-risky pattern (new_function_used). Review and replace if possible.
app/static/static/js/main.641d6522.js:2 New function used
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: vincenzo000915-cmd/ai-quant
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — app/static/static/js/main.641d6522.js:2
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/LegalPage.js:56
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/Pricing.js:277
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 — app/static/static/js/main.641d6522.js:2
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 — frontend/src/auth.js:141
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 — frontend/src/components/ProfitTargetCard.js:130
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 — frontend/src/pages/AdminAuditLog.js:36
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 — frontend/src/pages/Dashboard.js:219
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 — frontend/src/pages/Settings.js:126
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 — frontend/src/pages/Strategies.js:294
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 — frontend/src/pages/Trades.js:83
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/.claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
frontend/.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, 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 quality Integrity conf 1.00 7 occurrences Frontend route `/checkout` has no Link/navigate to it — frontend/src/App.js
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
7 occurrences
repo-level (7 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in app/static/static/js/main.641d6522.js:2
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
app/static/static/js/main.641d6522.js:2 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/LegalPage.js:56
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/LegalPage.js:56 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/pages/Pricing.js:277
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/pages/Pricing.js:277 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/static/static/js/main.641d6522.js:2
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/static/static/js/main.641d6522.js:2 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/components/TradingViewWidget.js:43
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/components/TradingViewWidget.js:43 Direct innerhtml assignment
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 26 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
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
translate_pending_cron.sh Ports
low System graph quality Integrity conf 1.00 19 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_INITIAL_EMAIL`, `ADMIN_INITIAL_PASSWORD`, `API_AUTH_TOKEN`, `BSCSCAN_API_KEY`, `CANDIDATE_CLEANUP_DAYS`, `CLAUDE_CLI_MAX_CONCURRENT`, `CLAUDE_CLI_TIMEOUT`, `CLAUDE_CLI_WAIT_TIMEOUT` + 11 more. Add them (with a placeholder/comment) to .env.ex…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 291 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph security security conf 1.00 Insecure pattern 'debug_true' in run.py:6
Found a known-risky pattern (debug_true). Review and replace if possible.
run.py:6 Debug true
low System graph quality Tests conf 1.00 Low test-to-source ratio
24 tests / 194 src (ratio 0.12).
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/site_audit.py:send_telegram, scripts/review_daily_ai_improve.py:send_tg 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 26 places
Functions with the same first-5-line body hash: app/models.py:to_dict, app/models.py:to_dict, app/models.py:to_dict, app/models.py:to_dict 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.
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: app/services/user_scope.py:wrapped, app/services/user_scope.py:wrapped, app/services/user_scope.py:wrapped, app/services/user_scope.py:wrapped This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hy…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `days_old` in app/tasks/strategy_tasks.py:3234
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 `seg_old` in scripts/test_segment_mae_regression.py:2
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `stopped_old` in scripts/flow_watchdog.py:386
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 `strategy_synthesize_v2` in app/services/candidate_pipeline.py:516
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 `strategy_synthesize_v2` in app/services/gatekeeper_learning.py:8
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 `strategy_synthesize_v2` in scripts/audit_range_menu.py:19
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 `strategy_synthesize_v2` in scripts/audit_range_menu_mtf.py:17
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `synthesize_strategy_v2` in app/services/llm_prompts/strategy_synthesize_v2.py:761
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: check_ai_improve_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:165
low System graph software Dead code conf 1.00 Possibly dead Python function: check_celery_beat_alive
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:263
low System graph software Dead code conf 1.00 Possibly dead Python function: check_celery_beat_heartbeat
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: check_celery_worker_ping
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:250
low System graph software Dead code conf 1.00 Possibly dead Python function: check_claude_cli_auth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:257
low System graph software Dead code conf 1.00 Possibly dead Python function: check_directional_concentration
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:482
low System graph software Dead code conf 1.00 Possibly dead Python function: check_disk_space
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:205
low System graph software Dead code conf 1.00 Possibly dead Python function: check_docker_containers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: check_dynamic_synth_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:468
low System graph software Dead code conf 1.00 Possibly dead Python function: check_exchange_connectivity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:297
low System graph software Dead code conf 1.00 Possibly dead Python function: check_llm_errors_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:238
low System graph software Dead code conf 1.00 Possibly dead Python function: check_logic_health_risk_params
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:510
low System graph software Dead code conf 1.00 Possibly dead Python function: check_market_brief_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:403
low System graph software Dead code conf 1.00 Possibly dead Python function: check_okx_connectivity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:312
low System graph software Dead code conf 1.00 Possibly dead Python function: check_pg_pool
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:281
low System graph software Dead code conf 1.00 Possibly dead Python function: check_postgres_health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: check_ram_load
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:226
low System graph software Dead code conf 1.00 Possibly dead Python function: check_recent_critical_events
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:341
low System graph software Dead code conf 1.00 Possibly dead Python function: check_reconcile_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:355
low System graph software Dead code conf 1.00 Possibly dead Python function: check_redis_health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: check_running_strategies
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:373
low System graph software Dead code conf 1.00 Possibly dead Python function: check_signal_cycle_15m
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: check_ssl_cert
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:185
low System graph software Dead code conf 1.00 Possibly dead Python function: check_telegram_bot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:329
low System graph software Dead code conf 1.00 Possibly dead Python function: check_translate_cron
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:366
low System graph software Dead code conf 1.00 Possibly dead Python function: check_translate_pipeline
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/flow_watchdog.py:198
low System graph software Dead code conf 1.00 Possibly dead Python function: check_web_local
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:153
low System graph software Dead code conf 1.00 Possibly dead Python function: check_web_prod
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/site_audit.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: f
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/mirror_experiment.py:37
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/src/services/okxWebSocket.js:59
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /account
`app/routes.py` declares `ANY /account` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /advisor/auto-apply/history
`app/routes.py` declares `ANY /advisor/auto-apply/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /advisor/auto-apply/run
`app/routes.py` declares `ANY /advisor/auto-apply/run` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /advisor/recommendations
`app/routes.py` declares `ANY /advisor/recommendations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /anomaly/check
`app/routes.py` declares `ANY /anomaly/check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /backtests/latest
`app/routes.py` declares `ANY /backtests/latest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /backtests/run-all
`app/routes.py` declares `ANY /backtests/run-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /candidates/<int:cid>/run-backtest
`app/routes.py` declares `ANY /candidates/<int:cid>/run-backtest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /gatekeeper/dashboard
`app/routes.py` declares `ANY /gatekeeper/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /gatekeeper/synthesize
`app/routes.py` declares `ANY /gatekeeper/synthesize` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /halt
`app/routes.py` declares `ANY /halt` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /halt/check
`app/routes.py` declares `ANY /halt/check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /killswitch
`app/routes.py` declares `ANY /killswitch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /manual-order
`app/routes.py` declares `ANY /manual-order` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /market/<path:symbol>/chart
`app/routes.py` declares `ANY /market/<path:symbol>/chart` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /market/<path:symbol>/price
`app/routes.py` declares `ANY /market/<path:symbol>/price` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /market/btc-chart
`app/routes.py` declares `ANY /market/btc-chart` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /market/btc-price
`app/routes.py` declares `ANY /market/btc-price` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /me/ai-activity-log
`app/routes.py` declares `ANY /me/ai-activity-log` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /me/diagnose
`app/routes.py` declares `ANY /me/diagnose` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /me/personal-advice
`app/routes.py` declares `ANY /me/personal-advice` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /me/recommendation-explain
`app/routes.py` declares `ANY /me/recommendation-explain` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /me/weekly-review
`app/routes.py` declares `ANY /me/weekly-review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /orders
`app/routes.py` declares `ANY /orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pnl/history
`app/routes.py` declares `ANY /pnl/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /pnl/summary
`app/routes.py` declares `ANY /pnl/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /positions
`app/routes.py` declares `ANY /positions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /preflight
`app/routes.py` declares `ANY /preflight` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /reconcile
`app/routes.py` declares `ANY /reconcile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /simulation/estimate
`app/routes.py` declares `ANY /simulation/estimate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>
`app/routes.py` declares `ANY /strategies/<int: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: ANY /strategies/<int:id>/apply-params
`app/routes.py` declares `ANY /strategies/<int:id>/apply-params` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/backtest
`app/routes.py` declares `ANY /strategies/<int:id>/backtest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/backtest/all
`app/routes.py` declares `ANY /strategies/<int:id>/backtest/all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/explain
`app/routes.py` declares `ANY /strategies/<int:id>/explain` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/fan-out
`app/routes.py` declares `ANY /strategies/<int:id>/fan-out` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/optimize
`app/routes.py` declares `ANY /strategies/<int:id>/optimize` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/optimize/latest
`app/routes.py` declares `ANY /strategies/<int:id>/optimize/latest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/retire
`app/routes.py` declares `ANY /strategies/<int:id>/retire` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/revive
`app/routes.py` declares `ANY /strategies/<int:id>/revive` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/<int:id>/start
`app/routes.py` declares `ANY /strategies/<int:id>/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: ANY /strategies/<int:id>/stop
`app/routes.py` declares `ANY /strategies/<int:id>/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: ANY /strategies/health/check
`app/routes.py` declares `ANY /strategies/health/check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /strategies/live-state
`app/routes.py` declares `ANY /strategies/live-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: ANY /strategies/performance
`app/routes.py` declares `ANY /strategies/performance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /symbols
`app/routes.py` declares `ANY /symbols` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /telegram/test
`app/routes.py` declares `ANY /telegram/test` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /trade-view/<path:symbol>
`app/routes.py` declares `ANY /trade-view/<path: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: ANY /trades
`app/routes.py` declares `ANY /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: ANY /unhalt
`app/routes.py` declares `ANY /unhalt` 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: app/models.py (1242 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/routes.py (3929 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/gatekeeper_learning.py (1282 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/gatekeeper_live.py (1797 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/llm_prompts/strategy_recommend.py (1230 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/strategy_advisor.py (1390 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/tasks/strategy_tasks.py (4522 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/Strategies.js (982 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/seed_catalog.py (1294 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/05e97889-f54a-426c-a19b-5eb7cb812237/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/05e97889-f54a-426c-a19b-5eb7cb812237/

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.