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

sulav1234567/nepse

https://github.com/sulav1234567/nepse · scanned 2026-06-16 00:25 UTC (2 months, 2 weeks ago)

102 raw signals (0 security + 102 graph)

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

Complete repo analysis

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

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

Showing 94 of 96 actionable findings. 102 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: DELETE /api/broker/meroshare (src/lib/broker-client.ts:86)
`src/lib/broker-client.ts:86` calls `DELETE /api/broker/meroshare` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/meroshare` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/broker/tms (src/lib/broker-client.ts:114)
`src/lib/broker-client.ts:114` calls `DELETE /api/broker/tms` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/tms` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/broker/meroshare/portfolio (src/lib/broker-client.ts:82)
`src/lib/broker-client.ts:82` calls `GET /api/broker/meroshare/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/meroshare/portfolio` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/broker/meroshare/status (src/lib/broker-client.ts:78)
`src/lib/broker-client.ts:78` calls `GET /api/broker/meroshare/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/meroshare/status` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/broker/tms/portfolio (src/lib/broker-client.ts:110)
`src/lib/broker-client.ts:110` calls `GET /api/broker/tms/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/tms/portfolio` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/broker/tms/status (src/lib/broker-client.ts:106)
`src/lib/broker-client.ts:106` calls `GET /api/broker/tms/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/tms/status` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/broker/meroshare/connect (src/lib/broker-client.ts:71)
`src/lib/broker-client.ts:71` calls `POST /api/broker/meroshare/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/meroshare/connect` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/broker/tms/connect (src/lib/broker-client.ts:99)
`src/lib/broker-client.ts:99` calls `POST /api/broker/tms/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/broker/tms/connect` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `autonomous_build_training_dataset` without auth dependency — backend/autonomous/api.py:94
`@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/autonomous/api.py:94 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `autonomous_evaluate_outcomes` without auth dependency — backend/autonomous/api.py:117
`@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/autonomous/api.py:117 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `autonomous_refresh_signals` without auth dependency — backend/autonomous/api.py:57
`@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/autonomous/api.py:57 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `autonomous_run_ingestion` without auth dependency — backend/autonomous/api.py:89
`@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/autonomous/api.py:89 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `autonomous_run_training` without auth dependency — backend/autonomous/api.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.
backend/autonomous/api.py:112 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trader_connect_broker` without auth dependency — backend/autonomous/api.py:168
`@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/autonomous/api.py:168 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trader_force_exit` without auth dependency — backend/autonomous/api.py:242
`@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/autonomous/api.py:242 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trader_manual_trade` without auth dependency — backend/autonomous/api.py:254
`@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/autonomous/api.py:254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trader_run_cycle` without auth dependency — backend/autonomous/api.py:146
`@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/autonomous/api.py:146 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in backend/broker/tms_client.py:80
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
backend/broker/tms_client.py:80 Tls verify false
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/api-client.ts:29
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/server.py:52
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/server.py:52 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/lib/auth-context.tsx:49
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/lib/auth-context.tsx:49 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/colab_continuous_train.py:46
`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 17 placeholder/mock markers across 7 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 quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 71 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
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 23 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.
backend/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/nepse_fetcher.py:fetch_nepse_index_history, backend/nepse_fetcher.py:fetch_nepse_index_history 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…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/nepse_fetcher.py:fetch_today_prices, backend/nepse_fetcher.py:fetch_today_prices, backend/nepse_fetcher.py:fetch_today_prices This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). C…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/autonomous/models.py:predict_frame, backend/autonomous/models.py:predict_frame, backend/autonomous/models.py:predict_frame, backend/autonomous/models.py:predict This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — se…
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: backend/autonomous/models.py:predict_latest, backend/autonomous/models.py:predict_latest, backend/autonomous/models.py:predict_latest, backend/autonomous/models.py:predict_latest This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
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/autonomous/models.py:train, backend/autonomous/models.py:train, backend/autonomous/models.py:train, backend/autonomous/models.py:train 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 software Dead code conf 1.00 Possibly dead Python function: cancel_order
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/broker/tms_client.py:242
low System graph software Dead code conf 1.00 Possibly dead Python function: compute_fibonacci_levels
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/engine.py:109
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_sector_indices
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/nepse_fetcher.py:880
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_fernet_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/security.py:112
low System graph software Dead code conf 1.00 Possibly dead Python function: stable_rng
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/deterministic.py:21
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 /meroshare
`backend/broker/api.py` declares `DELETE /meroshare` 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/ai/feature-importance
`backend/server.py` declares `GET /api/ai/feature-importance` 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/ai/model-metrics
`backend/server.py` declares `GET /api/ai/model-metrics` 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/ai/prediction/{symbol}
`backend/server.py` declares `GET /api/ai/prediction/{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: GET /api/ai/predictions
`backend/server.py` declares `GET /api/ai/predictions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/me
`backend/server.py` declares `GET /api/auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`backend/server.py` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/live/market
`backend/server.py` declares `GET /api/live/market` 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/live/stocks
`backend/server.py` declares `GET /api/live/stocks` 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/market
`backend/server.py` declares `GET /api/market` 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/market/index-analysis
`backend/server.py` declares `GET /api/market/index-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/market/index-history
`backend/server.py` declares `GET /api/market/index-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/market/intelligence
`backend/server.py` declares `GET /api/market/intelligence` 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/market/nepse-index
`backend/server.py` declares `GET /api/market/nepse-index` 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/market/regime
`backend/server.py` declares `GET /api/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/market/sectors
`backend/server.py` declares `GET /api/market/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/portfolio
`backend/server.py` declares `GET /api/portfolio` 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/predictions/daily
`backend/server.py` declares `GET /api/predictions/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: GET /api/predictions/monthly
`backend/server.py` declares `GET /api/predictions/monthly` 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/predictions/weekly
`backend/server.py` declares `GET /api/predictions/weekly` 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/stocks
`backend/server.py` declares `GET /api/stocks` 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/stocks/{symbol}
`backend/server.py` declares `GET /api/stocks/{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: GET /api/stocks/{symbol}/history
`backend/server.py` declares `GET /api/stocks/{symbol}/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 /backtests/latest
`backend/autonomous/api.py` declares `GET /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: GET /dashboard
`backend/autonomous/api.py` declares `GET /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: GET /meroshare/portfolio
`backend/broker/api.py` declares `GET /meroshare/portfolio` 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 /meroshare/status
`backend/broker/api.py` declares `GET /meroshare/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 /signals
`backend/autonomous/api.py` declares `GET /signals` 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 /signals/refresh/status
`backend/autonomous/api.py` declares `GET /signals/refresh/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 /signals/{symbol}
`backend/autonomous/api.py` declares `GET /signals/{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: GET /system/status
`backend/autonomous/api.py` declares `GET /system/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 /tms/status
`backend/broker/api.py` declares `GET /tms/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 /trader/audit
`backend/autonomous/api.py` declares `GET /trader/audit` 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 /trader/portfolio
`backend/autonomous/api.py` declares `GET /trader/portfolio` 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 /trader/positions
`backend/autonomous/api.py` declares `GET /trader/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: GET /trader/recommendations
`backend/autonomous/api.py` declares `GET /trader/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 /trader/status
`backend/autonomous/api.py` declares `GET /trader/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 /trader/trades
`backend/autonomous/api.py` declares `GET /trader/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: POST /api/auth/logout
`backend/server.py` declares `POST /api/auth/logout` 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 /datasets/build
`backend/autonomous/api.py` declares `POST /datasets/build` 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 /ingestion/run
`backend/autonomous/api.py` declares `POST /ingestion/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 /meroshare/connect
`backend/broker/api.py` declares `POST /meroshare/connect` 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 /outcomes/evaluate
`backend/autonomous/api.py` declares `POST /outcomes/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 api Wiring conf 1.00 Unused endpoint: POST /signals/refresh
`backend/autonomous/api.py` declares `POST /signals/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 /tms/connect
`backend/broker/api.py` declares `POST /tms/connect` 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 /trader/connect
`backend/autonomous/api.py` declares `POST /trader/connect` 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 /trader/exit
`backend/autonomous/api.py` declares `POST /trader/exit` 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 /trader/manual-trade
`backend/autonomous/api.py` declares `POST /trader/manual-trade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /trader/run
`backend/autonomous/api.py` declares `POST /trader/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 /training/run
`backend/autonomous/api.py` declares `POST /training/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 quality Complexity conf 1.00 Very large file: backend/nepse_fetcher.py (1447 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/29b59a15-5e35-4ce2-a70a-960408609b6e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/29b59a15-5e35-4ce2-a70a-960408609b6e/

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.