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

sungwoowi/wevelStock

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

136 raw signals (0 security + 136 graph)

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

Complete repo analysis

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

JSON
Combined
53.6
/100
Security checks
54
0 findings
System graph
54
100.0% cov · 126 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 15 Medium 15 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 126 Crowd 0 Layer: Software 19 Frontend 6 Network 3 Cicd 1 Quality 37 Security 15 Api 45
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 53.6/100 with 100.0% coverage. It contains 3909 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 136 findings — concentrated in quality (47), api (45), software (19). Risk profile is high: 0 critical, 15 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 109 of 126 actionable findings. 136 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_watch` without auth dependency — server/api/positions.py:116
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/positions.py:116 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_watch` without auth dependency — server/api/positions.py:91
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/positions.py:91 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_watch` without auth dependency — server/api/positions.py:66
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/positions.py:66 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `briefing_resend` without auth dependency — server/api/briefings_on_demand.py:381
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/briefings_on_demand.py:381 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `briefing_run` without auth dependency — server/api/briefings_on_demand.py:194
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/briefings_on_demand.py:194 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mark_notifications_read` without auth dependency — server/api/notifications.py:47
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/notifications.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_analyst_chat_stream` without auth dependency — server/api/analyst_chat.py:90
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/analyst_chat.py:90 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_analyst_chat` without auth dependency — server/api/analyst_chat.py:53
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/analyst_chat.py:53 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_production_chat_stream` without auth dependency — server/api/production_chat.py:203
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/production_chat.py:203 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_production_chat` without auth dependency — server/api/production_chat.py:103
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/production_chat.py:103 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_strategist_chat_stream` without auth dependency — server/api/strategist_chat.py:98
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/strategist_chat.py:98 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_strategist_chat` without auth dependency — server/api/strategist_chat.py:56
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/strategist_chat.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_snapshots` without auth dependency — server/api/infra.py:19
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/infra.py:19 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reload_config` without auth dependency — server/api/config.py:43
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/config.py:43 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_pipeline` without auth dependency — server/api/pipelines.py:49
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
server/api/pipelines.py:49 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — webapp/src/app/production-chat/page.tsx:246
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 — webapp/src/components/nav/AppShell.tsx:51
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 — webapp/src/lib/api.ts:5
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/resume.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.
.claude/commands/resume.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/wrap-up.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.
.claude/commands/wrap-up.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: mcp-servers/_template/CLAUDE.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.
mcp-servers/_template/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: server/CLAUDE.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.
server/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: webapp/CLAUDE.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.
webapp/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph 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 140 placeholder/mock markers across 34 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 23 in use
Port 23 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/defaults.yaml Ports
medium System graph network Security conf 1.00 Privileged port 55 in use
Port 55 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/defaults.yaml Ports
medium System graph network Security conf 1.00 Privileged port 58 in use
Port 58 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/defaults.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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 362 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 quality Integrity conf 1.00 11 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: pipelines/_base.py:run, pipelines/_base.py:run 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.
11 occurrences
repo-level (11 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: collectors/news_source.py:fetch, collectors/news_source.py:fetch, collectors/news_source.py:fetch, collectors/news_source.py:fetch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
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: collectors/screening.py:reload_screening_config, collectors/market_view.py:reload_market_view_config, collectors/score_inputs_config.py:reload_score_inputs_config, collectors/news_source.py:reload_news_source_config This is *the* AI-coder failure mod…
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 `macro_v1` in tests/test_snapshot_extend_db.py:82
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 server/api/briefings_on_demand.py:80
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 `run_backup` in server/schedulers/jobs/__init__.py:15
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 `run_backup` in server/schedulers/jobs/backup.py:16
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 `run_old` in tests/test_parts_store.py:57
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_build_pipeline_prompt_without_canon_categories_legacy` in tests/test_compose_canon_categories.py:172
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_kpi_period_filter_excludes_old` in tests/test_guidance_kpi.py:114
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_seed_analysts_v2` in tests/test_data_analysts_v2.py:126
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_buy_score_inputs_md
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
collectors/buy_score_inputs.py:382
low System graph software Dead code conf 1.00 Possibly dead Python function: build_flow_inputs_md
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
collectors/flow_inputs.py:256
low System graph software Dead code conf 1.00 Possibly dead Python function: build_s_score_inputs_md
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
collectors/screening_inputs.py:300
low System graph software Dead code conf 1.00 Possibly dead Python function: build_technicals_md
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
collectors/technicals.py:308
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_accounts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:198
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_briefing_now
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:103
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_briefing_pre
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:123
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_briefing_pre_force
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:149
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_help
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:264
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_retro
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:220
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_wealth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/telegram/commands.py:241
low System graph software Dead code conf 1.00 Possibly dead Python function: db_ohlc_provider
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/account/desk.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: investor_trend
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
connectors/kis/client.py:483
low System graph software Dead code conf 1.00 Possibly dead Python function: market_investor_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
connectors/kis/client.py:876
low System graph software Dead code conf 1.00 Possibly dead Python function: now_isoformat_with_tz
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/outputs.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: register_team_schedules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
server/schedulers/loader.py:104
low System graph software Dead code conf 1.00 Possibly dead Python function: render_market_overview
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/briefing/render.py:255
low System graph software Dead code conf 1.00 Possibly dead Python function: render_supply_sectors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/briefing/render.py:292
low System graph software Dead code conf 1.00 Possibly dead Python function: stock_investor_supply
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
connectors/krx/client.py:140
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/positions/watch/{position_id}
`server/api/positions.py` declares `DELETE /api/positions/watch/{position_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 /
`server/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/accounts
`server/api/accounts.py` declares `GET /api/accounts` 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/accounts/{account_id}/holdings
`server/api/accounts.py` declares `GET /api/accounts/{account_id}/holdings` 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/briefings/by-pipeline/{pipeline_id}/latest
`server/api/briefings.py` declares `GET /api/briefings/by-pipeline/{pipeline_id}/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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/briefings/feed
`server/api/briefings.py` declares `GET /api/briefings/feed` 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/briefings/{run_id}
`server/api/briefings.py` declares `GET /api/briefings/{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/config
`server/api/config.py` declares `GET /api/config` 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/config/llm
`server/api/config.py` declares `GET /api/config/llm` 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/desk/feed
`server/api/desk.py` declares `GET /api/desk/feed` 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/guidance/kpi
`server/api/guidance.py` declares `GET /api/guidance/kpi` 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/guidance/retrospective
`server/api/guidance.py` declares `GET /api/guidance/retrospective` 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
`server/main.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/market/history
`server/api/market.py` declares `GET /api/market/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/snapshot
`server/api/market.py` declares `GET /api/market/snapshot` 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/news/digest
`server/api/news.py` declares `GET /api/news/digest` 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/news/items
`server/api/news.py` declares `GET /api/news/items` 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/pipelines
`server/api/pipelines.py` declares `GET /api/pipelines` 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/pipelines/{pipeline_id}/latest
`server/api/pipelines.py` declares `GET /api/pipelines/{pipeline_id}/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 /api/positions/sim
`server/api/positions.py` declares `GET /api/positions/sim` 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/positions/watch
`server/api/positions.py` declares `GET /api/positions/watch` 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/teams
`server/api/teams.py` declares `GET /api/teams` 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/teams/{team_id}/latest
`server/api/teams.py` declares `GET /api/teams/{team_id}/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 /api/wealth/curve
`server/api/wealth.py` declares `GET /api/wealth/curve` 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/wealth/progress
`server/api/wealth.py` declares `GET /api/wealth/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 /notifications/recent
`server/api/notifications.py` declares `GET /notifications/recent` 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 /{analyst_id}
`server/api/analyst_chat.py` declares `GET /{analyst_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 /{pipeline_id}/latest
`server/api/briefings_on_demand.py` declares `GET /{pipeline_id}/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 /{pipeline_id}/latest/parts/{key}
`server/api/briefings_on_demand.py` declares `GET /{pipeline_id}/latest/parts/{key}` 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 /{pipeline_id}/recent
`server/api/briefings_on_demand.py` declares `GET /{pipeline_id}/recent` 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 /{strategist_id}
`server/api/strategist_chat.py` declares `GET /{strategist_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: PATCH /api/positions/watch/{position_id}
`server/api/positions.py` declares `PATCH /api/positions/watch/{position_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 /
`server/api/production_chat.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/config/reload
`server/api/config.py` declares `POST /api/config/reload` 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/pipelines/{pipeline_id}/run
`server/api/pipelines.py` declares `POST /api/pipelines/{pipeline_id}/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/positions/watch
`server/api/positions.py` declares `POST /api/positions/watch` 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/refresh-snapshots
`server/api/infra.py` declares `POST /api/refresh-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: POST /notifications/mark-read
`server/api/notifications.py` declares `POST /notifications/mark-read` 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 /stream
`server/api/production_chat.py` declares `POST /stream` 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 /{analyst_id}/chat
`server/api/analyst_chat.py` declares `POST /{analyst_id}/chat` 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 /{analyst_id}/chat/stream
`server/api/analyst_chat.py` declares `POST /{analyst_id}/chat/stream` 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 /{pipeline_id}/resend
`server/api/briefings_on_demand.py` declares `POST /{pipeline_id}/resend` 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 /{pipeline_id}/run
`server/api/briefings_on_demand.py` declares `POST /{pipeline_id}/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 /{strategist_id}/chat
`server/api/strategist_chat.py` declares `POST /{strategist_id}/chat` 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 /{strategist_id}/chat/stream
`server/api/strategist_chat.py` declares `POST /{strategist_id}/chat/stream` 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
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/93d5fb24-4fd2-4396-9f48-0c2315fe3b80/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/93d5fb24-4fd2-4396-9f48-0c2315fe3b80/

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.