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

ryokoralston/ai-research-policy-app

https://github.com/ryokoralston/ai-research-policy-app · scanned 2026-06-15 23:58 UTC (2 months, 3 weeks ago)

114 raw signals (0 security + 114 graph)

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

Complete repo analysis

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

JSON
Combined
69.2
/100
Security checks
69
0 findings
System graph
69
88.9% cov · 114 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 11 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 114 Crowd 0 Layer: Software 6 Frontend 4 Security 27 Cicd 1 Quality 16 Api 60
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 69.2/100 with 88.9% coverage. It contains 605 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 114 findings — concentrated in api (60), security (27), quality (16). Risk profile is high: 0 critical, 50 high, 11 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 106 of 114 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 api Wiring conf 1.00 Dangling fetch: DELETE /api/analysis/${id} (frontend/src/lib/api.ts:160)
`frontend/src/lib/api.ts:160` calls `DELETE /api/analysis/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/analysis/<p>` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/documents/${id} (frontend/src/lib/api.ts:118)
`frontend/src/lib/api.ts:118` calls `DELETE /api/documents/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<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: DELETE /api/reminders/${id} (frontend/src/lib/api.ts:196)
`frontend/src/lib/api.ts:196` calls `DELETE /api/reminders/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/reminders/<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: DELETE /api/reports/${id} (frontend/src/lib/api.ts:151)
`frontend/src/lib/api.ts:151` calls `DELETE /api/reports/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/reports/<p>` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/research/${id} (frontend/src/lib/api.ts:90)
`frontend/src/lib/api.ts:90` calls `DELETE /api/research/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/research/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/analysis/ (frontend/src/lib/api.ts:157)
`frontend/src/lib/api.ts:157` calls `GET /api/analysis/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/analysis` 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/analysis/${id} (frontend/src/lib/api.ts:158)
`frontend/src/lib/api.ts:158` calls `GET /api/analysis/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/analysis/<p>` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/status (frontend/src/lib/api.ts:200)
`frontend/src/lib/api.ts:200` calls `GET /api/auth/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/status` 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/digest/settings (frontend/src/lib/api.ts:228)
`frontend/src/lib/api.ts:228` calls `GET /api/digest/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/digest/settings` 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/digest/status (frontend/src/lib/api.ts:217)
`frontend/src/lib/api.ts:217` calls `GET /api/digest/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/digest/status` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents/${id} (frontend/src/lib/api.ts:116)
`frontend/src/lib/api.ts:116` calls `GET /api/documents/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/reports/ (frontend/src/lib/api.ts:143)
`frontend/src/lib/api.ts:143` calls `GET /api/reports/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/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/reports/${id} (frontend/src/lib/api.ts:144)
`frontend/src/lib/api.ts:144` calls `GET /api/reports/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/reports/<p>` 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/research/ (frontend/src/lib/api.ts:87)
`frontend/src/lib/api.ts:87` calls `GET /api/research/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/research` 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/research/${id} (frontend/src/lib/api.ts:88)
`frontend/src/lib/api.ts:88` calls `GET /api/research/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/research/<p>` 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/settings/models (frontend/src/lib/api.ts:165)
`frontend/src/lib/api.ts:165` calls `GET /api/settings/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/models` 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: PATCH /api/reports/${id} (frontend/src/lib/api.ts:146)
`frontend/src/lib/api.ts:146` calls `PATCH /api/reports/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/reports/<p>` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/login (frontend/src/lib/api.ts:202)
`frontend/src/lib/api.ts:202` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` 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/digest/send-now (frontend/src/lib/api.ts:210)
`frontend/src/lib/api.ts:210` calls `POST /api/digest/send-now` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/digest/send-now` 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: POST /api/documents/assign-folder (frontend/src/lib/api.ts:120)
`frontend/src/lib/api.ts:120` calls `POST /api/documents/assign-folder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/assign-folder` 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: POST /api/documents/ingest-url (frontend/src/lib/api.ts:110)
`frontend/src/lib/api.ts:110` calls `POST /api/documents/ingest-url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/ingest-url` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/rename-folder (frontend/src/lib/api.ts:125)
`frontend/src/lib/api.ts:125` calls `POST /api/documents/rename-folder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/rename-folder` 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: POST /api/reports/draft (frontend/src/lib/api.ts:139)
`frontend/src/lib/api.ts:139` calls `POST /api/reports/draft` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/reports/draft` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/research/${sessionId}/save-to-library (frontend/src/lib/api.ts:94)
`frontend/src/lib/api.ts:94` calls `POST /api/research/${sessionId}/save-to-library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/research/<p>/save-to-library` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/research/start (frontend/src/lib/api.ts:83)
`frontend/src/lib/api.ts:83` calls `POST /api/research/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/research/start` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/digest/settings (frontend/src/lib/api.ts:245)
`frontend/src/lib/api.ts:245` calls `PUT /api/digest/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/digest/settings` 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: PUT /api/settings/models (frontend/src/lib/api.ts:178)
`frontend/src/lib/api.ts:178` calls `PUT /api/settings/models` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/settings/models` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI DELETE `delete_analysis` without auth dependency — backend/routers/analysis.py:87
`@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/routers/analysis.py:87 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_debate` without auth dependency — backend/routers/debate.py:103
`@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/routers/debate.py:103 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_document` without auth dependency — backend/routers/documents.py:333
`@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/routers/documents.py:333 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_reminder` without auth dependency — backend/routers/reminders.py:17
`@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/routers/reminders.py:17 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_report` without auth dependency — backend/routers/reports.py:162
`@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/routers/reports.py:162 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_session` without auth dependency — backend/routers/research.py:128
`@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/routers/research.py:128 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_report` without auth dependency — backend/routers/reports.py:82
`@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/routers/reports.py:82 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ask_documents` without auth dependency — backend/routers/documents.py:356
`@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/routers/documents.py:356 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `assign_folder` without auth dependency — backend/routers/documents.py:299
`@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/routers/documents.py:299 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_draft` without auth dependency — backend/routers/reports.py:54
`@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/routers/reports.py:54 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_report` without auth dependency — backend/routers/reports.py:18
`@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/routers/reports.py:18 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_url` without auth dependency — backend/routers/documents.py:225
`@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/routers/documents.py:225 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `rename_folder` without auth dependency — backend/routers/documents.py:315
`@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/routers/documents.py:315 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_session_to_library` without auth dependency — backend/routers/research.py:86
`@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/routers/research.py:86 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `send_now` without auth dependency — backend/routers/digest.py:131
`@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/routers/digest.py:131 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_analysis` without auth dependency — backend/routers/analysis.py:15
`@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/routers/analysis.py:15 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_debate` without auth dependency — backend/routers/debate.py:26
`@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/routers/debate.py:26 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_research` without auth dependency — backend/routers/research.py:20
`@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/routers/research.py:20 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_document` without auth dependency — backend/routers/documents.py:185
`@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/routers/documents.py:185 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `save_model_settings` without auth dependency — backend/routers/settings.py:46
`@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/routers/settings.py:46 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `save_settings_endpoint` without auth dependency — backend/routers/digest.py:91
`@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/routers/digest.py:91 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/security-patterns.yaml:15
Found a known-risky pattern (eval_used). Review and replace if possible.
.claude/security-patterns.yaml:15 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in .claude/security-patterns.yaml:15
Found a known-risky pattern (exec_used). Review and replace if possible.
.claude/security-patterns.yaml:15 Exec used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/layout/ThemeProvider.tsx:67
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api.ts:29
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/security-patterns.yaml
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/security-patterns.yaml VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in .claude/security-patterns.yaml:25
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
.claude/security-patterns.yaml:25 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/layout/ThemeProvider.tsx:67
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/layout/ThemeProvider.tsx:67 Dangerous innerhtml
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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 47 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 88 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 99 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 security security conf 1.00 Insecure pattern 'document_write' in frontend/src/app/debate/page.tsx:227
Found a known-risky pattern (document_write). Review and replace if possible.
frontend/src/app/debate/page.tsx:227 Document write
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/routers/reports.py:generate_report, backend/routers/reports.py:create_draft This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: build_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/evals/eval_research_queries.py:113
low System graph software Dead code conf 1.00 Possibly dead Python function: build_prompt_with_example
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/evals/eval_research_queries.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: execute_tool
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/rag_service.py:141
low System graph software Dead code conf 1.00 Possibly dead Python function: process_bind_param
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/secret_crypto.py:89
low System graph software Dead code conf 1.00 Possibly dead Python function: process_result_value
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/secret_crypto.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: require_auth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/auth.py:52
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 /{analysis_id}
`backend/routers/analysis.py` declares `DELETE /{analysis_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: DELETE /{debate_id}
`backend/routers/debate.py` declares `DELETE /{debate_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: DELETE /{doc_id}
`backend/routers/documents.py` declares `DELETE /{doc_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: DELETE /{reminder_id}
`backend/routers/reminders.py` declares `DELETE /{reminder_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: DELETE /{report_id}
`backend/routers/reports.py` declares `DELETE /{report_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: DELETE /{session_id}
`backend/routers/research.py` declares `DELETE /{session_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/routers/reports.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 /models
`backend/routers/settings.py` declares `GET /models` 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 /settings
`backend/routers/digest.py` declares `GET /settings` 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 /template/{report_type}
`backend/routers/reports.py` declares `GET /template/{report_type}` 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 /{analysis_id}
`backend/routers/analysis.py` declares `GET /{analysis_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 /{analysis_id}/export
`backend/routers/analysis.py` declares `GET /{analysis_id}/export` 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 /{debate_id}
`backend/routers/debate.py` declares `GET /{debate_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 /{debate_id}/stream
`backend/routers/debate.py` declares `GET /{debate_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 /{doc_id}
`backend/routers/documents.py` declares `GET /{doc_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 /{report_id}
`backend/routers/reports.py` declares `GET /{report_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 /{report_id}/export
`backend/routers/reports.py` declares `GET /{report_id}/export` 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 /{session_id}
`backend/routers/research.py` declares `GET /{session_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 /{session_id}/stream
`backend/routers/research.py` declares `GET /{session_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: PATCH /{report_id}
`backend/routers/reports.py` declares `PATCH /{report_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ask
`backend/routers/documents.py` declares `POST /ask` 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 /assign-folder
`backend/routers/documents.py` declares `POST /assign-folder` 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 /draft
`backend/routers/reports.py` declares `POST /draft` 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 /generate
`backend/routers/reports.py` declares `POST /generate` 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 /ingest-url
`backend/routers/documents.py` declares `POST /ingest-url` 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 /login
`backend/routers/auth.py` declares `POST /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 /rename-folder
`backend/routers/documents.py` declares `POST /rename-folder` 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 /send-now
`backend/routers/digest.py` declares `POST /send-now` 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 /start
`backend/routers/debate.py` declares `POST /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 /upload
`backend/routers/documents.py` declares `POST /upload` 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 /{session_id}/save-to-library
`backend/routers/research.py` declares `POST /{session_id}/save-to-library` 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: PUT /models
`backend/routers/settings.py` declares `PUT /models` 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: PUT /settings
`backend/routers/digest.py` declares `PUT /settings` 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/69866e6f-10d3-4ca5-9d83-78df59229cdd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/69866e6f-10d3-4ca5-9d83-78df59229cdd/

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.