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

tjgksmf1012/stock_chart_helper

https://github.com/tjgksmf1012/stock_chart_helper · scanned 2026-06-16 00:37 UTC (2 months, 2 weeks ago)

111 raw signals (0 security + 111 graph)

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

Complete repo analysis

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

JSON
Combined
66.2
/100
Security checks
66
0 findings
System graph
66
100.0% cov · 102 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 8 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 102 Crowd 0 Layer: Software 4 Frontend 5 Hardware 5 Security 18 Quality 21 Api 49
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 66.2/100 with 100.0% coverage. It contains 1337 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 111 findings — concentrated in api (49), quality (30), security (18). Risk profile is high: 0 critical, 17 high, 16 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 92 of 102 actionable findings. 111 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 security auth conf 1.00 FastAPI DELETE `delete_outcome` without auth dependency — backend/app/api/routes/outcomes.py:560
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/outcomes.py:560 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `remove_from_watchlist` without auth dependency — backend/app/api/routes/watchlist.py:47
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/watchlist.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_outcome` without auth dependency — backend/app/api/routes/outcomes.py:542
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/outcomes.py:542 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_to_watchlist` without auth dependency — backend/app/api/routes/watchlist.py:37
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/watchlist.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dashboard_scan_refresh` without auth dependency — backend/app/api/routes/dashboard.py:323
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/dashboard.py:323 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `evaluate_pending_outcomes` without auth dependency — backend/app/api/routes/outcomes.py:404
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/outcomes.py:404 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `prime_kis_runtime` without auth dependency — backend/app/api/routes/system.py:617
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:617 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `record_outcome` without auth dependency — backend/app/api/routes/outcomes.py:377
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/outcomes.py:377 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_pattern_stats` without auth dependency — backend/app/api/routes/patterns.py:306
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/patterns.py:306 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_alert_check_now` without auth dependency — backend/app/api/routes/system.py:637
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:637 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_screener` without auth dependency — backend/app/api/routes/screener.py:36
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/screener.py:36 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `send_test_alert` without auth dependency — backend/app/api/routes/system.py:622
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:622 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sync_watchlist` without auth dependency — backend/app/api/routes/watchlist.py:29
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/watchlist.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_intraday_candidate_warmup_background` without auth dependency — backend/app/api/routes/system.py:800
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:800 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_intraday_warmup_background` without auth dependency — backend/app/api/routes/system.py:785
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:785 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `warmup_intraday_cache` without auth dependency — backend/app/api/routes/system.py:577
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:577 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `warmup_intraday_candidates` without auth dependency — backend/app/api/routes/system.py:592
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/routes/system.py:592 securityAuth fastapi unauth mutation
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.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/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/.claude/launch.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/launch.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. 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: backend/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 9 occurrences Frontend route `ai` has no Link/navigate to it — frontend/src/main.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
9 occurrences
repo-level (9 hits)
Orphan pageWiring
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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 hardware Supply chain conf 1.00 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.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/api/routes/patterns.py:get_pattern_library, backend/app/api/routes/patterns.py:get_pattern 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…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: backend/app/api/routes/dashboard.py:dashboard_long, backend/app/api/routes/dashboard.py:dashboard_short, backend/app/api/routes/dashboard.py:dashboard_similarity, backend/app/api/routes/dashboard.py:dashboard_no_signal This is *the* AI-coder failure …
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 `model_copy` in backend/app/services/ai_recommendation_service.py:454
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 `model_copy` in backend/app/services/openai_recommendation_service.py:33
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: build_rows
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/data_fetcher.py:567
low System graph software Dead code conf 1.00 Possibly dead Python function: prune_scan_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/scan_history_service.py:273
low System graph software Dead code conf 1.00 Possibly dead Python function: run_scheduled_intraday_warmup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/routes/system.py:757
low System graph software Dead code conf 1.00 Possibly dead Python function: run_scheduled_outcome_evaluation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/routes/outcomes.py:479
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: ANY /
`backend/app/main.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/{code}
`backend/app/api/routes/watchlist.py` declares `DELETE /api/v1/{code}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/{outcome_id}
`backend/app/api/routes/outcomes.py` declares `DELETE /api/v1/{outcome_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
`backend/app/api/routes/outcomes.py` declares `GET /api/v1` 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/calibration
`backend/app/api/routes/outcomes.py` declares `GET /api/v1/calibration` 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/calibration/offline
`backend/app/api/routes/outcomes.py` declares `GET /api/v1/calibration/offline` 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/forming-candidates
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/forming-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/high-textbook-similarity
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/high-textbook-similarity` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/intraday/warmup-status
`backend/app/api/routes/system.py` declares `GET /api/v1/intraday/warmup-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/kis/prime-status
`backend/app/api/routes/system.py` declares `GET /api/v1/kis/prime-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/library
`backend/app/api/routes/patterns.py` declares `GET /api/v1/library` 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/library/{pattern_type}
`backend/app/api/routes/patterns.py` declares `GET /api/v1/library/{pattern_type}` 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: GET /api/v1/live-intraday-candidates
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/live-intraday-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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/long-high-probability
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/long-high-probability` 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: GET /api/v1/market-regime
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/market-regime` 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/overview
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/overview` 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/pattern-armed
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/pattern-armed` 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/recommendations
`backend/app/api/routes/ai.py` declares `GET /api/v1/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: GET /api/v1/scan-history
`backend/app/api/routes/system.py` declares `GET /api/v1/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/scan-quality-report
`backend/app/api/routes/system.py` declares `GET /api/v1/scan-quality-report` 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/scan-status
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/scan-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/search
`backend/app/api/routes/symbols.py` declares `GET /api/v1/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/sector-heatmap
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/sector-heatmap` 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/short-high-probability
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/short-high-probability` 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/stats
`backend/app/api/routes/patterns.py` declares `GET /api/v1/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/status
`backend/app/api/routes/system.py` declares `GET /api/v1/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/summary
`backend/app/api/routes/outcomes.py` declares `GET /api/v1/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: GET /api/v1/watchlist-no-signal
`backend/app/api/routes/dashboard.py` declares `GET /api/v1/watchlist-no-signal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/{symbol}/analysis
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/analysis` 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/{symbol}/bars
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/bars` 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/{symbol}/deep-analysis
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/deep-analysis` 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: GET /api/v1/{symbol}/deep-analysis/progress
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/deep-analysis/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/{symbol}/money-flow
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/money-flow` 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/{symbol}/price
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{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: GET /api/v1/{symbol}/reference-cases
`backend/app/api/routes/symbols.py` declares `GET /api/v1/{symbol}/reference-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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/{outcome_id}
`backend/app/api/routes/outcomes.py` declares `PATCH /api/v1/{outcome_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: POST /api/v1
`backend/app/api/routes/outcomes.py` declares `POST /api/v1` 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/add
`backend/app/api/routes/watchlist.py` declares `POST /api/v1/add` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/alerts/run-check
`backend/app/api/routes/system.py` declares `POST /api/v1/alerts/run-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: POST /api/v1/alerts/test
`backend/app/api/routes/system.py` declares `POST /api/v1/alerts/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: POST /api/v1/evaluate-pending
`backend/app/api/routes/outcomes.py` declares `POST /api/v1/evaluate-pending` 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/intraday/warmup
`backend/app/api/routes/system.py` declares `POST /api/v1/intraday/warmup` 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/intraday/warmup-candidates
`backend/app/api/routes/system.py` declares `POST /api/v1/intraday/warmup-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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/intraday/warmup-candidates/background
`backend/app/api/routes/system.py` declares `POST /api/v1/intraday/warmup-candidates/background` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/intraday/warmup/background
`backend/app/api/routes/system.py` declares `POST /api/v1/intraday/warmup/background` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/kis/prime
`backend/app/api/routes/system.py` declares `POST /api/v1/kis/prime` 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/run
`backend/app/api/routes/screener.py` declares `POST /api/v1/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: POST /api/v1/scan-refresh
`backend/app/api/routes/dashboard.py` declares `POST /api/v1/scan-refresh` 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/stats/refresh
`backend/app/api/routes/patterns.py` declares `POST /api/v1/stats/refresh` 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: backend/app/services/analysis_service.py (3695 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/pattern_engine.py (1542 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/scanner.py (1816 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/ChartPage.tsx (1142 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/DashboardPage.tsx (1444 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/1d6ebe09-647d-40eb-a4e9-cd422b8bf744/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1d6ebe09-647d-40eb-a4e9-cd422b8bf744/

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.