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

tuannguyen-create/fbot

https://github.com/tuannguyen-create/fbot · scanned 2026-06-16 00:43 UTC (2 months, 1 week ago)

202 raw signals (0 security + 202 graph)

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

Complete repo analysis

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

JSON
Combined
46.9
/100
Security checks
47
0 findings
System graph
47
100.0% cov · 178 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 17 Medium 21 Low 83 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 178 Crowd 0 Layer: Software 14 Frontend 3 Network 4 Hardware 5 Cicd 1 Quality 84 Security 16 Api 51
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 46.9/100 with 100.0% coverage. It contains 5664 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 202 findings — concentrated in quality (98), api (51), software (23). Risk profile is high: 0 critical, 17 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 120 of 178 actionable findings. 202 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 api Wiring conf 1.00 Dangling fetch: GET /api/bctc-ctck${qs} (frontend/components/BctcCtckPanel.tsx:53)
`frontend/components/BctcCtckPanel.tsx:53` calls `GET /api/bctc-ctck${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bctc-ctck/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `close_position` without auth dependency — app/api/portfolio.py:154
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/portfolio.py:154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_cash` without auth dependency — app/api/portfolio.py:166
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/portfolio.py:166 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_position` without auth dependency — app/api/portfolio.py:133
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/portfolio.py:133 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_ticker_m3_settings` without auth dependency — app/api/watchlist.py:71
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/watchlist.py:71 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_position` without auth dependency — app/api/portfolio.py:112
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/portfolio.py:112 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_run` without auth dependency — app/api/validation_replay.py:48
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/validation_replay.py:48 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_run` without auth dependency — app/api/veto_tuning.py:60
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/veto_tuning.py:60 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `evaluate_now` without auth dependency — app/api/nav_risk.py:92
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/nav_risk.py:92 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_ai_note` without auth dependency — app/api/review_workbench.py:131
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/review_workbench.py:131 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_case_from_nav_risk` without auth dependency — app/api/review_workbench.py:172
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/review_workbench.py:172 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_case_from_tactical` without auth dependency — app/api/review_workbench.py:163
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/review_workbench.py:163 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_decision` without auth dependency — app/api/review_workbench.py:110
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/review_workbench.py:110 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_escalate` without auth dependency — app/api/review_workbench.py:150
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/review_workbench.py:150 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_nav_baseline` without auth dependency — app/api/portfolio.py:182
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/portfolio.py:182 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_thresholds` without auth dependency — app/api/settings.py:81
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/settings.py:81 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/stock/[ticker]/ClusterProgress.tsx:42
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/app/stock/[ticker]/page.tsx:242
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/app/watchlist/page.tsx:50
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/BctcCtckPanel.tsx:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/components/HeSoPanel.tsx:61
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/components/PlacedVolumePanel.tsx:54
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/components/SectorRotationCard.tsx:56
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/components/ShareholderAnchorPanel.tsx:69
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/components/SubjectInferencePanel.tsx:66
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: AGENTS.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. 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 — app/main.py:27
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph 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 55 placeholder/mock markers across 26 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 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
config/he_so_config.yaml Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
config/he_so_config.yaml Ports
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.
config/he_so_config.yaml Ports
medium System graph network Security conf 1.00 Privileged port 45 in use
Port 45 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
config/he_so_config.yaml Ports
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 324 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-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 1, 7
frontend/Dockerfile:1, 7 (2 hits)
containersPinned dependencies
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 quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/probe_fiinquant_fundamentals.py:main, scripts/probe_fiinquant_capabilities.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: app/services/notification.py:send_cycle_breakout_email, app/services/notification.py:send_cycle_10day_warning_email, app/services/notification.py:send_cycle_bottom_email This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 31 places
Functions with the same first-5-line body hash: app/services/candle_metrics_service.py:inject_deps, app/services/cost_per_holder_service.py:inject_deps, app/services/placed_volume_service.py:inject_deps, app/services/validation_case_service.py:inject_deps This is *the* AI-coder failure mode (4× mo…
duplicatesduplication
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/run_validation_labeling.py:main, scripts/run_backtest.py:main, scripts/run_calibration.py:main, scripts/run_validation_replay.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hyg…
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: app/adapters/money_flow_source.py:get_sector_flow, app/adapters/money_flow_source.py:get_sector_flow, app/adapters/money_flow_source.py:get_sector_flow, app/adapters/money_flow_source.py:get_sector_flow This is *the* AI-coder failure mode (4× more du…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: app/adapters/placed_volume_source.py:get_placed_volume, app/adapters/placed_volume_source.py:get_placed_volume, app/adapters/placed_volume_source.py:get_placed_volume, app/adapters/placed_volume_source.py:get_placed_volume This is *the* AI-coder fail…
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 `test_api_has_503_and_404_copy` in tests/unit/test_cluster_volume_service.py:478
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 `test_api_has_503_and_404_copy` in tests/unit/test_order_rate_service.py:464
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: classify_ownership
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/notification_governance.py:253
low System graph software Dead code conf 1.00 5 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
5 files, 5 locations
alembic/versions/001_initial_schema.py:180
alembic/versions/002_add_indexes.py:34
alembic/versions/020_phase3_nav_risk.py:76
alembic/versions/021_stop_monitor_eval.py:71
alembic/versions/022_portfolio_constraint_eval.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_intraday_bars_blocking
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/fiinquant_rest.py:395
low System graph software Dead code conf 1.00 Possibly dead Python function: format_time_ict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/utils/timezone.py:30
low System graph software Dead code conf 1.00 Possibly dead Python function: is_individual_drawdown_eligible
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/domain/bridge_foot.py:245
low System graph software Dead code conf 1.00 Possibly dead Python function: is_trading_day_db
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/market_calendar.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/operator_efficiency_service.py:360
low System graph software Dead code conf 1.00 Possibly dead Python function: process_minute_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/holder_minute_service.py:206
low System graph software Dead code conf 1.00 Possibly dead Python function: regime_policy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/domain/regime.py:546
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_client
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/fiinquant_eod_investor.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_state
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/nav_monitor.py:38
low System graph software Dead code conf 1.00 6 occurrences Possibly dead Python function: run_eod
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
6 files, 6 locations
app/services/deception_service.py:575
app/services/model_chan_cau_service.py:620
app/services/model_dien_ho_service.py:506
app/services/model_mu_sat_canh_buom_service.py:541
app/services/model_ngua_dut_day_service.py:514
app/services/model_z_service.py:519
low System graph software Dead code conf 1.00 Possibly dead Python function: run_monitor_loop
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/nav_monitor.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: to_utc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/utils/timezone.py:19
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 api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/notifications/mutes/{ticker}/{channel}
`app/api/notifications.py` declares `DELETE /api/v1/notifications/mutes/{ticker}/{channel}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`app/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/calibration/runs
`app/api/calibration.py` declares `GET /api/calibration/runs` 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/divergence/scan
`app/api/divergence.py` declares `GET /api/divergence/scan` 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/divergence/sectors
`app/api/divergence.py` declares `GET /api/divergence/sectors` 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/v1/admin/replay-runs
`app/api/admin.py` declares `GET /api/v1/admin/replay-runs` 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/v1/admin/replay-runs/{run_id}
`app/api/admin.py` declares `GET /api/v1/admin/replay-runs/{run_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/v1/admin/scan-history
`app/api/admin.py` declares `GET /api/v1/admin/scan-history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/admin/scan-m1-history
`app/api/admin.py` declares `GET /api/v1/admin/scan-m1-history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/cycles
`app/api/cycles.py` declares `GET /api/v1/cycles` 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/v1/cycles/candidates
`app/api/cycles.py` declares `GET /api/v1/cycles/candidates` 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/v1/cycles/{cycle_id}
`app/api/cycles.py` declares `GET /api/v1/cycles/{cycle_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/v1/health
`app/main.py` declares `GET /api/v1/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/v1/notifications/mutes
`app/api/notifications.py` declares `GET /api/v1/notifications/mutes` 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/v1/notifications/review
`app/api/notifications.py` declares `GET /api/v1/notifications/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: GET /api/v1/ownership/review/export.csv
`app/api/ownership_snapshots.py` declares `GET /api/v1/ownership/review/export.csv` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/ownership/snapshots
`app/api/ownership_snapshots.py` declares `GET /api/v1/ownership/snapshots` 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/v1/ownership/snapshots/{ticker}
`app/api/ownership_snapshots.py` declares `GET /api/v1/ownership/snapshots/{ticker}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/stream/alerts
`app/api/stream.py` declares `GET /api/v1/stream/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 /audit/{case_id}
`app/api/review_workbench.py` declares `GET /audit/{case_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 /cases
`app/api/review_workbench.py` declares `GET /cases` 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 /cases/{case_id}
`app/api/review_workbench.py` declares `GET /cases/{case_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 /cluster/{ticker}/history
`app/api/cluster_volume.py` declares `GET /cluster/{ticker}/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cluster/{ticker}/progress
`app/api/cluster_volume.py` declares `GET /cluster/{ticker}/progress` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /history
`app/api/nav_risk.py` declares `GET /history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /hs1-hs2/history
`app/api/hs1_hs2.py` declares `GET /hs1-hs2/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /order-rate/watchlist
`app/api/order_rate.py` declares `GET /order-rate/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: GET /order-rate/{ticker}
`app/api/order_rate.py` declares `GET /order-rate/{ticker}` 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 /order-rate/{ticker}/series
`app/api/order_rate.py` declares `GET /order-rate/{ticker}/series` 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 /queue
`app/api/review_workbench.py` declares `GET /queue` 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 /{run_id}
`app/api/cycle_state.py` declares `GET /{run_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 /{ticker}
`app/api/stop_monitor.py` declares `GET /{ticker}` 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 /{ticker}/summary
`app/api/watchlist.py` declares `GET /{ticker}/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: PATCH /{ticker}/m3
`app/api/watchlist.py` declares `PATCH /{ticker}/m3` 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 /
`app/api/cycle_state.py` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/he-so/scan
`app/api/he_so.py` declares `POST /api/he-so/scan` 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/v1/admin/backfill-daily
`app/api/admin.py` declares `POST /api/v1/admin/backfill-daily` 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/v1/admin/backfill-intraday
`app/api/admin.py` declares `POST /api/v1/admin/backfill-intraday` 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/v1/admin/cleanup-stuck-runs
`app/api/admin.py` declares `POST /api/v1/admin/cleanup-stuck-runs` 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/v1/admin/replay-m1-history
`app/api/admin.py` declares `POST /api/v1/admin/replay-m1-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: POST /api/v1/admin/replay-m3-history
`app/api/admin.py` declares `POST /api/v1/admin/replay-m3-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: POST /api/v1/admin/sync-watchlist
`app/api/admin.py` declares `POST /api/v1/admin/sync-watchlist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/notifications/mutes
`app/api/notifications.py` declares `POST /api/v1/notifications/mutes` 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/v1/ownership/proxy-scan
`app/api/ownership_snapshots.py` declares `POST /api/v1/ownership/proxy-scan` 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 /cases/from-nav-risk/{recommendation_id}
`app/api/review_workbench.py` declares `POST /cases/from-nav-risk/{recommendation_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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /cases/from-tactical/{candidate_id}
`app/api/review_workbench.py` declares `POST /cases/from-tactical/{candidate_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /cases/{case_id}/ai-note
`app/api/review_workbench.py` declares `POST /cases/{case_id}/ai-note` 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 /cases/{case_id}/decision
`app/api/review_workbench.py` declares `POST /cases/{case_id}/decision` 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 /cases/{case_id}/escalate
`app/api/review_workbench.py` declares `POST /cases/{case_id}/escalate` 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 /evaluate
`app/api/nav_risk.py` declares `POST /evaluate` 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/services/calibration_service.py (1373 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/validation_replay_service.py (1715 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/veto_tuning_service.py (1196 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/validation/page.tsx (1500 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/9cd79a8d-1c35-4fc9-8f7b-271232df24a4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9cd79a8d-1c35-4fc9-8f7b-271232df24a4/

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.