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

wevo7526/quantOS

https://github.com/wevo7526/quantOS · scanned 2026-06-16 00:56 UTC (2 months, 1 week ago)

222 raw signals (0 security + 222 graph)

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

Complete repo analysis

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

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

Showing 154 of 207 actionable findings. 222 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/me/connectors/${connectorId} (frontend/lib/api.ts:438)
`frontend/lib/api.ts:438` calls `DELETE /api/me/connectors/${connectorId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/connectors/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/me/monitors/${monitorId} (frontend/lib/api.ts:455)
`frontend/lib/api.ts:455` calls `DELETE /api/me/monitors/${monitorId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/monitors/<p>` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/me/reports/${reportId} (frontend/lib/api.ts:424)
`frontend/lib/api.ts:424` calls `DELETE /api/me/reports/${reportId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports/<p>` 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/me/reports/${reportId}/share (frontend/lib/api.ts:430)
`frontend/lib/api.ts:430` calls `DELETE /api/me/reports/${reportId}/share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports/<p>/share` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/alerts/unread-count (frontend/lib/api.ts:464)
`frontend/lib/api.ts:464` calls `GET /api/me/alerts/unread-count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/alerts/unread-count` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/breadth (frontend/lib/api.ts:471)
`frontend/lib/api.ts:471` calls `GET /api/me/breadth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/breadth` 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/me/connectors (frontend/lib/api.ts:434)
`frontend/lib/api.ts:434` calls `GET /api/me/connectors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/connectors` 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/me/journal?${q.toString()} (frontend/lib/api.ts:412)
`frontend/lib/api.ts:412` calls `GET /api/me/journal?${q.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/journal` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/reports (frontend/lib/api.ts:418)
`frontend/lib/api.ts:418` calls `GET /api/me/reports` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports` 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/me/theses?${q.toString()} (frontend/lib/api.ts:392)
`frontend/lib/api.ts:392` calls `GET /api/me/theses?${q.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/theses` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/me/workspaces (frontend/lib/api.ts:379)
`frontend/lib/api.ts:379` calls `GET /api/me/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/workspaces` 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/me/workspaces/${workspaceId}/mandate (frontend/lib/api.ts:383)
`frontend/lib/api.ts:383` calls `GET /api/me/workspaces/${workspaceId}/mandate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/workspaces/<p>/mandate` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/alerts/${alertId} (frontend/lib/api.ts:467)
`frontend/lib/api.ts:467` calls `PATCH /api/me/alerts/${alertId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/alerts/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/monitors/${monitorId} (frontend/lib/api.ts:453)
`frontend/lib/api.ts:453` calls `PATCH /api/me/monitors/${monitorId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/monitors/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/reports/${reportId} (frontend/lib/api.ts:422)
`frontend/lib/api.ts:422` calls `PATCH /api/me/reports/${reportId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/me/theses/${thesisId} (frontend/lib/api.ts:409)
`frontend/lib/api.ts:409` calls `PATCH /api/me/theses/${thesisId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/theses/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/alerts/mark-all-read (frontend/lib/api.ts:465)
`frontend/lib/api.ts:465` calls `POST /api/me/alerts/mark-all-read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/alerts/mark-all-read` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/connectors (frontend/lib/api.ts:436)
`frontend/lib/api.ts:436` calls `POST /api/me/connectors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/connectors` 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: POST /api/me/journal (frontend/lib/api.ts:417)
`frontend/lib/api.ts:417` calls `POST /api/me/journal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/journal` 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: POST /api/me/monitors (frontend/lib/api.ts:451)
`frontend/lib/api.ts:451` calls `POST /api/me/monitors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/monitors` 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: POST /api/me/monitors/${monitorId}/run (frontend/lib/api.ts:459)
`frontend/lib/api.ts:459` calls `POST /api/me/monitors/${monitorId}/run` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/monitors/<p>/run` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/reports (frontend/lib/api.ts:420)
`frontend/lib/api.ts:420` calls `POST /api/me/reports` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports` 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: POST /api/me/reports/${reportId}/share (frontend/lib/api.ts:428)
`frontend/lib/api.ts:428` calls `POST /api/me/reports/${reportId}/share` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/reports/<p>/share` 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: POST /api/me/theses (frontend/lib/api.ts:395)
`frontend/lib/api.ts:395` calls `POST /api/me/theses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/theses` 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: POST /api/me/theses/generate (frontend/lib/api.ts:399)
`frontend/lib/api.ts:399` calls `POST /api/me/theses/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/theses/generate` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/me/workspaces (frontend/lib/api.ts:381)
`frontend/lib/api.ts:381` calls `POST /api/me/workspaces` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/workspaces` 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: PUT /api/me/workspaces/${workspaceId}/mandate (frontend/lib/api.ts:385)
`frontend/lib/api.ts:385` calls `PUT /api/me/workspaces/${workspaceId}/mandate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me/workspaces/<p>/mandate` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI DELETE `delete_monitor` without auth dependency — backend/routes/alphaflow.py:845
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:845 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_my_data` without auth dependency — backend/routes/alphaflow.py:912
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:912 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_report` without auth dependency — backend/routes/alphaflow.py:445
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:445 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `revoke_connector` without auth dependency — backend/routes/alphaflow.py:373
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:373 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `unshare_report` without auth dependency — backend/routes/alphaflow.py:463
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:463 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `rename_workspace` without auth dependency — backend/routes/alphaflow.py:101
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:101 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `set_alert_state` without auth dependency — backend/routes/alphaflow.py:893
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:893 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_monitor` without auth dependency — backend/routes/alphaflow.py:833
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:833 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_report` without auth dependency — backend/routes/alphaflow.py:434
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:434 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_thesis` without auth dependency — backend/routes/alphaflow.py:296
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:296 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `alerts_mark_all_read` without auth dependency — backend/routes/alphaflow.py:887
`@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/routes/alphaflow.py:887 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_connector` without auth dependency — backend/routes/alphaflow.py:358
`@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/routes/alphaflow.py:358 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_journal` without auth dependency — backend/routes/alphaflow.py:330
`@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/routes/alphaflow.py:330 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_monitor` without auth dependency — backend/routes/alphaflow.py:820
`@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/routes/alphaflow.py:820 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_report` without auth dependency — backend/routes/alphaflow.py:399
`@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/routes/alphaflow.py:399 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_thesis` without auth dependency — backend/routes/alphaflow.py:276
`@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/routes/alphaflow.py:276 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_workspace` without auth dependency — backend/routes/alphaflow.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/routes/alphaflow.py:94 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_thesis_route` without auth dependency — backend/routes/alphaflow.py:157
`@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/routes/alphaflow.py:157 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `quick_signal` without auth dependency — backend/routes/alphaflow.py:481
`@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/routes/alphaflow.py:481 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_monitor_now` without auth dependency — backend/routes/alphaflow.py:853
`@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/routes/alphaflow.py:853 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `share_report` without auth dependency — backend/routes/alphaflow.py:454
`@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/routes/alphaflow.py:454 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_thesis` without auth dependency — backend/routes/alphaflow.py:206
`@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/routes/alphaflow.py:206 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_mandate` without auth dependency — backend/routes/alphaflow.py:124
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routes/alphaflow.py:124 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/portal/page.tsx:887
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/hooks/useAnalysis.ts:272
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/lib/api.ts:574
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: mcp-server/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
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 39 placeholder/mock markers across 12 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 quality Integrity conf 1.00 26 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AF_MAX_MONITORS`, `AF_MAX_THESES`, `AF_MAX_WORKSPACES`, `ALPHAENGINE_KEY`, `ALPHAENGINE_URL`, `ALPHAFLOW_ENC_KEY`, `CORS_ORIGINS`, `DESK_SESSION_TTL_SECONDS` + 18 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't br…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 11 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: node:20-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.10.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.
mcp-server/Dockerfile:8 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.13-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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/components/ApiKeys.tsx:157
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 15 places
Functions with the same first-5-line body hash: mcp-server/contracts/inbound.py:assert_ready, mcp-server/contracts/inbound.py:assert_ready, mcp-server/contracts/inbound.py:assert_ready, mcp-server/contracts/inbound.py:assert_ready This is *the* AI-coder failure mode (4× more duplication in vibe-co…
duplicatesduplication
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: mcp-server/seam/data_context.py:get_provided_data, mcp-server/seam/data_context.py:get_provided 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 sep…
11 occurrences
repo-level (11 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: mcp-server/telemetry.py:record_mcp_current, mcp-server/telemetry.py:record_mcp, mcp-server/telemetry.py:record This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
5 occurrences
repo-level (5 hits)
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/db/alphaflow_repositories.py:get, backend/db/alphaflow_repositories.py:rename, backend/db/alphaflow_repositories.py:get, backend/db/alphaflow_repositories.py:get This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: backend/db/alphaflow_repositories.py:create, backend/db/alphaflow_repositories.py:create, backend/db/alphaflow_repositories.py:create, backend/db/alphaflow_repositories.py:create This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
2 occurrences
repo-level (2 hits)
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_snapshot_legacy` in backend/main.py:1299
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 `resolutions_dict_unused` in backend/infra/citations_resolver.py:317
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: add_many
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/provenance/store.py:179
low System graph software Dead code conf 1.00 Possibly dead Python function: ahttp_get_json
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/http.py:247
low System graph software Dead code conf 1.00 Possibly dead Python function: best_effort_sections
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/nlp/sections.py:84
low System graph software Dead code conf 1.00 Possibly dead Python function: correlation_heatmap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/exports/charts.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: draw
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/exports/pdf_renderer.py:310
low System graph software Dead code conf 1.00 Possibly dead Python function: drawdown_chart
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/exports/charts.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: gather_bounded
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/async_utils.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: heartbeat
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/status_store.py:42
low System graph software Dead code conf 1.00 Possibly dead Python function: http_get_json
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/http.py:148
low System graph software Dead code conf 1.00 Possibly dead Python function: render_scan
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/exports/pdf_renderer.py:1266
low System graph software Dead code conf 1.00 Possibly dead Python function: run_interpreter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/orchestrator.py:236
low System graph software Dead code conf 1.00 Possibly dead Python function: run_strategy
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/orchestrator.py:369
low System graph software Dead code conf 1.00 Possibly dead Python function: run_sync_with_timeout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/async_utils.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: run_synthesizer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/orchestrator.py:1236
low System graph software Dead code conf 1.00 Possibly dead Python function: run_with_timeout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/infra/http.py:274
low System graph software Dead code conf 1.00 Possibly dead Python function: to_citation_index
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/provenance/store.py:225
low System graph software Dead code conf 1.00 Possibly dead Python function: universe_by_class
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/universe.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: wrap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/exports/pdf_renderer.py:307
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 quality Integrity conf 1.00 Stub function `_none_key` (body is just `pass`/`return`) — backend/infra/provided_data.py:201
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `_none_key` (body is just `pass`/`return`) — mcp-server/seam/install.py:44
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`mcp-server/api.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/data/events
`backend/main.py` declares `GET /api/data/events` 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/export/memo/{memo_id}
`backend/main.py` declares `GET /api/export/memo/{memo_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/export/morning
`backend/main.py` declares `GET /api/export/morning` 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/export/portfolio
`backend/main.py` declares `GET /api/export/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/export/range
`backend/main.py` declares `GET /api/export/range` 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/export/scorecard
`backend/main.py` declares `GET /api/export/scorecard` 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/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/me/risk
`backend/main.py` declares `GET /api/me/risk` 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/equity-curve
`backend/main.py` declares `GET /api/portfolio/equity-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/portfolio/risk
`backend/main.py` declares `GET /api/portfolio/risk` 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/quant/correlation
`backend/main.py` declares `GET /api/quant/correlation` 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/quant/cross-asset-correlation
`backend/main.py` declares `GET /api/quant/cross-asset-correlation` 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/quant/drawdown/{ticker}
`backend/main.py` declares `GET /api/quant/drawdown/{ticker}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/quant/enrich
`backend/main.py` declares `GET /api/quant/enrich` 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/quant/factors
`backend/main.py` declares `GET /api/quant/factors` 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/quant/macro-series
`backend/main.py` declares `GET /api/quant/macro-series` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/quant/options/{ticker}
`backend/main.py` declares `GET /api/quant/options/{ticker}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/quant/regime/diagnostics
`backend/main.py` declares `GET /api/quant/regime/diagnostics` 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/quant/volatility/{ticker}
`backend/main.py` declares `GET /api/quant/volatility/{ticker}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/ready
`backend/main.py` declares `GET /api/ready` 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/track-record/verify
`backend/main.py` declares `GET /api/track-record/verify` 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 /favicon.svg
`mcp-server/api.py` declares `GET /favicon.svg` 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 /icon.png
`mcp-server/api.py` declares `GET /icon.png` 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 /icon.svg
`mcp-server/api.py` declares `GET /icon.svg` 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 /v1/internal/usage
`mcp-server/api.py` declares `GET /v1/internal/usage` 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 /v1/jobs/{job_id}
`mcp-server/api.py` declares `GET /v1/jobs/{job_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 /v1/jobs/{job_id}/stream
`mcp-server/api.py` declares `GET /v1/jobs/{job_id}/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: GET /v1/status
`mcp-server/api.py` declares `GET /v1/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/tools
`mcp-server/api.py` declares `GET /v1/tools` 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 /v1/usage
`mcp-server/api.py` declares `GET /v1/usage` 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 /v1/version
`mcp-server/api.py` declares `GET /v1/version` 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/analyze/stream
`backend/main.py` declares `POST /api/analyze/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 /api/internal/apply-mandate
`backend/main.py` declares `POST /api/internal/apply-mandate` 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/internal/cron/nightly
`backend/main.py` declares `POST /api/internal/cron/nightly` 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/internal/desk
`backend/main.py` declares `POST /api/internal/desk` 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/internal/keys/verify
`backend/main.py` declares `POST /api/internal/keys/verify` 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/internal/slate
`backend/main.py` declares `POST /api/internal/slate` 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/internal/usage/incr
`backend/main.py` declares `POST /api/internal/usage/incr` 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/quant/curve/key-rate-durations
`backend/main.py` declares `POST /api/quant/curve/key-rate-durations` 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/track-record/anchor
`backend/main.py` declares `POST /api/track-record/anchor` 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 /v1/apply_mandate
`mcp-server/api.py` declares `POST /v1/apply_mandate` 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 /v1/desk/macro
`mcp-server/api.py` declares `POST /v1/desk/macro` 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 /v1/desk/research
`mcp-server/api.py` declares `POST /v1/desk/research` 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 /v1/desk/risk
`mcp-server/api.py` declares `POST /v1/desk/risk` 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 /v1/desk/scenario
`mcp-server/api.py` declares `POST /v1/desk/scenario` 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 /v1/desk/screen
`mcp-server/api.py` declares `POST /v1/desk/screen` 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 /v1/desk/structure
`mcp-server/api.py` declares `POST /v1/desk/structure` 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 /v1/jobs
`mcp-server/api.py` declares `POST /v1/jobs` 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 /v1/tools/{tool}
`mcp-server/api.py` declares `POST /v1/tools/{tool}` 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/agents/orchestrator.py (1727 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/exports/pdf_renderer.py (1544 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/main.py (4600 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/docs/page.tsx (1110 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/page.tsx (900 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/portal/page.tsx (2227 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/components/MemoPanel.tsx (1347 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/7dd9f62e-05a6-4390-8e3e-8130fa6a0d7e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7dd9f62e-05a6-4390-8e3e-8130fa6a0d7e/

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.