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

vaibhav4046/recoup

https://github.com/vaibhav4046/recoup · scanned 2026-06-16 00:46 UTC (2 months, 1 week ago)

85 raw signals (0 security + 85 graph)

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

Complete repo analysis

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

JSON
Combined
62.9
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 85 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 20 Medium 11 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 85 Crowd 0 Layer: Software 8 Hardware 5 Frontend 1 Security 25 Cicd 1 Quality 9 Api 36
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 62.9/100 with 100.0% coverage. It contains 454 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 85 findings — concentrated in api (36), security (25), quality (9). Risk profile is high: 0 critical, 20 high, 11 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 81 of 85 actionable findings. 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 POST `agent_autopilot` without auth dependency — backend/app/main.py:282
`@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/main.py:282 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_execute` without auth dependency — backend/app/main.py:267
`@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/main.py:267 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_plan` without auth dependency — backend/app/main.py:210
`@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/main.py:210 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_recover` without auth dependency — backend/app/main.py:223
`@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/main.py:223 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_run` without auth dependency — backend/app/main.py:332
`@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/main.py:332 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `approve` without auth dependency — backend/app/main.py:338
`@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/main.py:338 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `assistant_chat` without auth dependency — backend/app/main.py:254
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/main.py:254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `auth_logout` without auth dependency — backend/app/main.py:514
`@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/main.py:514 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `forget` without auth dependency — backend/app/main.py:590
`@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/main.py:590 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gmail_findings_post` without auth dependency — backend/app/main.py:579
`@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/main.py:579 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `magic_start` without auth dependency — backend/app/main.py:443
`@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/main.py:443 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mark_paid` without auth dependency — backend/app/main.py:369
`@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/main.py:369 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mark_sent` without auth dependency — backend/app/main.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/app/main.py:358 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mcp_ep` without auth dependency — backend/app/main.py:417
`@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/main.py:417 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mcp_ep` without auth dependency — backend/app/main.py:418
`@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/main.py:418 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mcp_proof` without auth dependency — backend/app/main.py:303
`@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/main.py:303 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reject` without auth dependency — backend/app/main.py:347
`@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/main.py:347 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `report` without auth dependency — backend/app/main.py:385
`@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/main.py:385 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `scan_ep` without auth dependency — backend/app/main.py:326
`@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/main.py:326 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `vector_seed` without auth dependency — backend/app/main.py:201
`@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/main.py:201 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — agent-timeline.js:75
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 — app.js:539
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 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: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in agent-timeline.js:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
agent-timeline.js:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app.js:32
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app.js:32 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.js:4
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.js:4 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in app.js:513
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
app.js:513 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in app.js:365
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
app.js:365 Insert adjacent html
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 Tests conf 1.00 Very low test-to-source ratio
3 test file(s) for 37 source file(s) (ratio 0.08). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 40 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_subscription_emails
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/gmail.py:228
low System graph software Dead code conf 1.00 Possibly dead Python function: google_callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:205
low System graph software Dead code conf 1.00 Possibly dead Python function: google_exchange
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: list_cases
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/mongodb.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: respond
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/assistant.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: run_mission
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/autopilot.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: run_preview
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/executor.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: stats_full
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/unclaimed.py:42
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: GET /api/audit
`backend/app/main.py` declares `GET /api/audit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/google/callback
`backend/app/main.py` declares `GET /api/auth/google/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/auth/google/start
`backend/app/main.py` declares `GET /api/auth/google/start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/magic/verify
`backend/app/main.py` declares `GET /api/auth/magic/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 /api/auth/me
`backend/app/main.py` declares `GET /api/auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/status
`backend/app/main.py` declares `GET /api/auth/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/gmail/callback
`backend/app/main.py` declares `GET /api/gmail/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/gmail/findings
`backend/app/main.py` declares `GET /api/gmail/findings` 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/gmail/start
`backend/app/main.py` declares `GET /api/gmail/start` 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/app/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/mcp
`backend/app/main.py` declares `GET /api/mcp` 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/mcp/proof
`backend/app/main.py` declares `GET /api/mcp/proof` 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/state
`backend/app/main.py` declares `GET /api/state` 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/unclaimed/search
`backend/app/main.py` declares `GET /api/unclaimed/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/unclaimed/stats
`backend/app/main.py` declares `GET /api/unclaimed/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /mcp
`backend/app/main.py` declares `GET /mcp` 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/account/forget
`backend/app/main.py` declares `POST /api/account/forget` 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/actions/{action_id}/approve
`backend/app/main.py` declares `POST /api/actions/{action_id}/approve` 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/actions/{action_id}/paid
`backend/app/main.py` declares `POST /api/actions/{action_id}/paid` 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/actions/{action_id}/reject
`backend/app/main.py` declares `POST /api/actions/{action_id}/reject` 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/actions/{action_id}/sent
`backend/app/main.py` declares `POST /api/actions/{action_id}/sent` 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/agent/autopilot
`backend/app/main.py` declares `POST /api/agent/autopilot` 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/agent/execute
`backend/app/main.py` declares `POST /api/agent/execute` 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/agent/plan
`backend/app/main.py` declares `POST /api/agent/plan` 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/agent/recover
`backend/app/main.py` declares `POST /api/agent/recover` 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/agent/run
`backend/app/main.py` declares `POST /api/agent/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/assistant
`backend/app/main.py` declares `POST /api/assistant` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/logout
`backend/app/main.py` declares `POST /api/auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/magic/start
`backend/app/main.py` declares `POST /api/auth/magic/start` 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/gmail/findings
`backend/app/main.py` declares `POST /api/gmail/findings` 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/mcp
`backend/app/main.py` declares `POST /api/mcp` 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/mcp/proof
`backend/app/main.py` declares `POST /api/mcp/proof` 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/report
`backend/app/main.py` declares `POST /api/report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/scan
`backend/app/main.py` declares `POST /api/scan` 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/vector/seed
`backend/app/main.py` declares `POST /api/vector/seed` 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 /mcp
`backend/app/main.py` declares `POST /mcp` 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: app.js (1517 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/122bf7a4-d093-40a9-bb36-e0f66dbf1697/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/122bf7a4-d093-40a9-bb36-e0f66dbf1697/

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.