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

smithadifd/investing_companion

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

121 raw signals (0 security + 121 graph)

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

Complete repo analysis

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

JSON
Combined
51.0
/100
Security checks
51
0 findings
System graph
51
100.0% cov · 99 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 7 Medium 4 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 99 Crowd 0 Layer: Software 9 Frontend 18 Hardware 1 Security 4 Cicd 2 Quality 10 Api 55
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 51.0/100 with 100.0% coverage. It contains 2308 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 121 findings — concentrated in api (55), quality (28), frontend (18). Risk profile is high: 2 critical, 7 high, 4 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in backend/scripts/seed_demo_users.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/scripts/seed_demo_users.py:33
critical System graph security Secrets conf 1.00 Possible secret in frontend/src/lib/demo.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/src/lib/demo.ts:5
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:152 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /accounts/${id} (frontend/src/lib/api/client.ts:1153)
`frontend/src/lib/api/client.ts:1153` calls `DELETE /accounts/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/accounts/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /lessons/${id} (frontend/src/lib/api/client.ts:1119)
`frontend/src/lib/api/client.ts:1119` calls `DELETE /lessons/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/lessons/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /trades/${id} (frontend/src/lib/api/client.ts:1071)
`frontend/src/lib/api/client.ts:1071` calls `DELETE /trades/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/trades/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/logout-all (frontend/src/lib/api/client.ts:304)
`frontend/src/lib/api/client.ts:304` calls `POST /auth/logout-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/logout-all` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/me/change-password (frontend/src/lib/api/client.ts:329)
`frontend/src/lib/api/client.ts:329` calls `POST /auth/me/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/me/change-password` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `refresh_tokens` without auth dependency — backend/app/api/v1/endpoints/auth.py:108
`@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/v1/endpoints/auth.py:108 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api/client.ts:209
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 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 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docs-site.yml CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 102 placeholder/mock markers across 27 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 44 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 cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 5 locations
.github/workflows/docs-site.yml:33, 47, 65 (3 hits)
.github/workflows/ci.yml:53, 85 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
45 tests / 236 src (ratio 0.19).
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/api/v1/endpoints/trade.py:get_trade_service, backend/app/api/v1/endpoints/trade.py:get_trade 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 th…
19 occurrences
repo-level (19 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_expired_sessions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/auth.py:249
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/env.py:56
low System graph software Dead code conf 1.00 Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/versions/20260201_005_add_economic_events.py:71
low System graph software Dead code conf 1.00 Possibly dead Python function: group_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/trade.py:552
low System graph software Dead code conf 1.00 Possibly dead Python function: seed_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/seed_demo_data.py:402
low System graph software Dead code conf 1.00 Possibly dead Python function: send_end_of_day_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/notifications/discord.py:529
low System graph software Dead code conf 1.00 Possibly dead Python function: send_movers_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/notifications/discord.py:334
low System graph software Dead code conf 1.00 Possibly dead Python function: send_upcoming_events
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/notifications/discord.py:429
low System graph software Dead code conf 1.00 Possibly dead Python function: shutdown_executor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/data_providers/yahoo.py:48
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/accounts/{account_id}
`backend/app/api/v1/endpoints/account.py` declares `DELETE /api/v1/accounts/{account_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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/schwab/disconnect
`backend/app/api/v1/endpoints/schwab.py` declares `DELETE /api/v1/schwab/disconnect` 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: DELETE /api/v1/trades/{trade_id}
`backend/app/api/v1/endpoints/trade.py` declares `DELETE /api/v1/trades/{trade_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/watchlists/{watchlist_id}
`backend/app/api/v1/endpoints/watchlist.py` declares `DELETE /api/v1/watchlists/{watchlist_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/{ratio_id}
`backend/app/api/v1/endpoints/ratio.py` declares `DELETE /api/v1/{ratio_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 /
`backend/app/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1
`backend/app/api/v1/endpoints/ratio.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/accounts
`backend/app/api/v1/endpoints/account.py` declares `GET /api/v1/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/v1/accounts/{account_id}
`backend/app/api/v1/endpoints/account.py` declares `GET /api/v1/accounts/{account_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/auth/me
`backend/app/api/v1/endpoints/auth.py` declares `GET /api/v1/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/v1/auth/me/sessions
`backend/app/api/v1/endpoints/auth.py` declares `GET /api/v1/auth/me/sessions` 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/auth/registration-status
`backend/app/api/v1/endpoints/auth.py` declares `GET /api/v1/auth/registration-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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/dashboard/exposure
`backend/app/api/v1/endpoints/dashboard.py` declares `GET /api/v1/dashboard/exposure` 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/dashboard/needs-attention
`backend/app/api/v1/endpoints/dashboard.py` declares `GET /api/v1/dashboard/needs-attention` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/dashboard/trade-readiness
`backend/app/api/v1/endpoints/dashboard.py` declares `GET /api/v1/dashboard/trade-readiness` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/quotes
`backend/app/api/v1/endpoints/ratio.py` declares `GET /api/v1/quotes` 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/schwab/callback
`backend/app/api/v1/endpoints/schwab.py` declares `GET /api/v1/schwab/callback` 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/schwab/status
`backend/app/api/v1/endpoints/schwab.py` declares `GET /api/v1/schwab/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/trades
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/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: GET /api/v1/trades/pairs
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/trades/pairs` 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/trades/performance
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/trades/performance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/trades/portfolio
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/trades/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/v1/trades/positions/{equity_id}
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/trades/positions/{equity_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/trades/{trade_id}
`backend/app/api/v1/endpoints/trade.py` declares `GET /api/v1/trades/{trade_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/watchlists
`backend/app/api/v1/endpoints/watchlist.py` declares `GET /api/v1/watchlists` 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/watchlists/movers
`backend/app/api/v1/endpoints/watchlist.py` declares `GET /api/v1/watchlists/movers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/watchlists/{watchlist_id}
`backend/app/api/v1/endpoints/watchlist.py` declares `GET /api/v1/watchlists/{watchlist_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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/{ratio_id}
`backend/app/api/v1/endpoints/ratio.py` declares `GET /api/v1/{ratio_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/{ratio_id}/history
`backend/app/api/v1/endpoints/ratio.py` declares `GET /api/v1/{ratio_id}/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/{ratio_id}/quote
`backend/app/api/v1/endpoints/ratio.py` declares `GET /api/v1/{ratio_id}/quote` 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/v1/auth/me
`backend/app/api/v1/endpoints/auth.py` declares `PATCH /api/v1/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: POST /api/v1
`backend/app/api/v1/endpoints/ratio.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/accounts
`backend/app/api/v1/endpoints/account.py` declares `POST /api/v1/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: POST /api/v1/auth/login
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/auth/login` 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/auth/logout
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/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 /api/v1/auth/logout-all
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/auth/logout-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/me/change-password
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/auth/me/change-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/auth/refresh
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/auth/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/auth/register
`backend/app/api/v1/endpoints/auth.py` declares `POST /api/v1/auth/register` 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/initialize
`backend/app/api/v1/endpoints/ratio.py` declares `POST /api/v1/initialize` 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/schwab/connect
`backend/app/api/v1/endpoints/schwab.py` declares `POST /api/v1/schwab/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 /api/v1/trades
`backend/app/api/v1/endpoints/trade.py` declares `POST /api/v1/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/v1/trades/position-size
`backend/app/api/v1/endpoints/trade.py` declares `POST /api/v1/trades/position-size` 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: POST /api/v1/watchlists
`backend/app/api/v1/endpoints/watchlist.py` declares `POST /api/v1/watchlists` 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/watchlists/{watchlist_id}/items
`backend/app/api/v1/endpoints/watchlist.py` declares `POST /api/v1/watchlists/{watchlist_id}/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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/accounts/{account_id}
`backend/app/api/v1/endpoints/account.py` declares `PUT /api/v1/accounts/{account_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/trades/{trade_id}
`backend/app/api/v1/endpoints/trade.py` declares `PUT /api/v1/trades/{trade_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/watchlists/{watchlist_id}
`backend/app/api/v1/endpoints/watchlist.py` declares `PUT /api/v1/watchlists/{watchlist_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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/watchlists/{watchlist_id}/items/{item_id}
`backend/app/api/v1/endpoints/watchlist.py` declares `PUT /api/v1/watchlists/{watchlist_id}/items/{item_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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/{ratio_id}
`backend/app/api/v1/endpoints/ratio.py` declares `PUT /api/v1/{ratio_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
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/526ec207-933e-4aa1-94b6-9dde86a5c197/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/526ec207-933e-4aa1-94b6-9dde86a5c197/

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.