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

yoonhj7173/craft

https://github.com/yoonhj7173/craft · scanned 2026-06-16 01:07 UTC (2 months, 1 week ago)

116 raw signals (0 security + 116 graph)

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

Complete repo analysis

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

JSON
Combined
52.3
/100
Security checks
52
0 findings
System graph
52
100.0% cov · 104 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 21 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 104 Crowd 0 Layer: Software 6 Frontend 6 Hardware 3 Security 27 Quality 21 Api 41
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.3/100 with 100.0% coverage. It contains 1146 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 116 findings — concentrated in api (41), quality (33), security (27). Risk profile is high: 0 critical, 20 high, 21 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph security auth conf 1.00 FastAPI DELETE `delete_agent` without auth dependency — backend/app/routers/teams.py:252
`@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/app/routers/teams.py:252 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_context` without auth dependency — backend/app/routers/context.py:85
`@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/app/routers/context.py:85 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_edge` without auth dependency — backend/app/routers/edges.py:56
`@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/app/routers/edges.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_memory` without auth dependency — backend/app/routers/memory.py:56
`@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/app/routers/memory.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_project` without auth dependency — backend/app/routers/projects.py:239
`@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/app/routers/projects.py:239 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_team` without auth dependency — backend/app/routers/teams.py:134
`@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/app/routers/teams.py:134 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `rename_project` without auth dependency — backend/app/routers/projects.py:225
`@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/app/routers/projects.py:225 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_agent` without auth dependency — backend/app/routers/teams.py:229
`@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/app/routers/teams.py:229 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_team` without auth dependency — backend/app/routers/teams.py:114
`@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/app/routers/teams.py:114 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_agent` without auth dependency — backend/app/routers/teams.py:179
`@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/routers/teams.py:179 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_team` without auth dependency — backend/app/routers/teams.py:68
`@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/routers/teams.py:68 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `continue_task` without auth dependency — backend/app/routers/tasks.py:57
`@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/routers/tasks.py:57 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_edge` without auth dependency — backend/app/routers/edges.py:27
`@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/routers/edges.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pause_project` without auth dependency — backend/app/routers/projects.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/routers/projects.py:254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resume_project` without auth dependency — backend/app/routers/projects.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/routers/projects.py:267 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stop_task` without auth dependency — backend/app/routers/tasks.py:38
`@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/routers/tasks.py:38 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_context` without auth dependency — backend/app/routers/context.py:30
`@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/routers/context.py:30 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_memory` without auth dependency — backend/app/routers/memory.py:38
`@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/app/routers/memory.py:38 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in claude-design-handoff/marketing/support.js:677
Found a known-risky pattern (new_function_used). Review and replace if possible.
claude-design-handoff/marketing/support.js:677 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in claude-design-handoff/product/support.js:677
Found a known-risky pattern (new_function_used). Review and replace if possible.
claude-design-handoff/product/support.js:677 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/blog/[slug]/page.tsx:40
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/page.tsx:32
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 — claude-design-handoff/marketing/support.js:968
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 — claude-design-handoff/product/support.js:968
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:12
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/agents/product_manager.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agents/product_manager.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/init.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/init.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/status.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/status.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
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/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. 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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/blog/[slug]/page.tsx:40
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/blog/[slug]/page.tsx:40 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/page.tsx:32
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/page.tsx:32 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in claude-design-handoff/marketing/support.js:422
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
claude-design-handoff/marketing/support.js:422 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in claude-design-handoff/product/support.js:422
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
claude-design-handoff/product/support.js:422 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in claude-design-handoff/marketing/support.js:44
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
claude-design-handoff/marketing/support.js:44 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in claude-design-handoff/product/support.js:44
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
claude-design-handoff/product/support.js:44 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in backend/app/services/sandbox.py:102
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
backend/app/services/sandbox.py:102 Subprocess shell true
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 40 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 14 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.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.
backend/Dockerfile:3 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/components/overlays/Overlays.tsx:159
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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/components/panels/InspectorPanel.tsx:123
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 Tests conf 1.00 Low test-to-source ratio
21 tests / 90 src (ratio 0.23).
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/services/filestore.py:put_text, backend/app/services/filestore.py:put_text 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.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/app/services/sandbox.py:create, backend/app/services/sandbox.py:create, backend/app/services/sandbox.py:create This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or d…
8 occurrences
repo-level (8 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 software Dead code conf 1.00 Possibly dead Python function: call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/crews/factory.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: format
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/logging_config.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: is_allowed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/extract.py:23
low System graph software Dead code conf 1.00 Possibly dead Python function: require_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:189
low System graph software Dead code conf 1.00 Possibly dead Python function: screenshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/verification.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: tenant_scope
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/auth.py:241
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 /agents/{agent_id}
`backend/app/routers/teams.py` declares `DELETE /agents/{agent_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 /agents/{agent_id}/memory
`backend/app/routers/memory.py` declares `DELETE /agents/{agent_id}/memory` 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 /context/{context_id}
`backend/app/routers/context.py` declares `DELETE /context/{context_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 /edges/{edge_id}
`backend/app/routers/edges.py` declares `DELETE /edges/{edge_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 /projects/{project_id}
`backend/app/routers/projects.py` declares `DELETE /projects/{project_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 /teams/{team_id}
`backend/app/routers/teams.py` declares `DELETE /teams/{team_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 /agents/{agent_id}
`backend/app/routers/teams.py` declares `GET /agents/{agent_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 /agents/{agent_id}/memory
`backend/app/routers/memory.py` declares `GET /agents/{agent_id}/memory` 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 /me
`backend/app/routers/auth_demo.py` declares `GET /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 /notifications
`backend/app/routers/realtime.py` declares `GET /notifications` 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 /outputs/{output_id}
`backend/app/routers/outputs.py` declares `GET /outputs/{output_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 /outputs/{output_id}/download
`backend/app/routers/outputs.py` declares `GET /outputs/{output_id}/download` 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 /projects
`backend/app/routers/projects.py` declares `GET /projects` 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 /projects/{project_id}
`backend/app/routers/projects.py` declares `GET /projects/{project_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 /projects/{project_id}/board
`backend/app/routers/realtime.py` declares `GET /projects/{project_id}/board` 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 /projects/{project_id}/chat/history
`backend/app/routers/chat.py` declares `GET /projects/{project_id}/chat/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /projects/{project_id}/context
`backend/app/routers/context.py` declares `GET /projects/{project_id}/context` 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 /projects/{project_id}/map
`backend/app/routers/projects.py` declares `GET /projects/{project_id}/map` 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 /projects/{project_id}/outputs
`backend/app/routers/outputs.py` declares `GET /projects/{project_id}/outputs` 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 /projects/{project_id}/sse
`backend/app/routers/realtime.py` declares `GET /projects/{project_id}/sse` 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 /projects/{project_id}/usage
`backend/app/routers/realtime.py` declares `GET /projects/{project_id}/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 /ready
`backend/app/routers/system.py` declares `GET /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 /tasks/{task_id}/outputs.zip
`backend/app/routers/outputs.py` declares `GET /tasks/{task_id}/outputs.zip` 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 /teams/{team_id}
`backend/app/routers/teams.py` declares `GET /teams/{team_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 /templates
`backend/app/routers/projects.py` declares `GET /templates` 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 /agents/{agent_id}
`backend/app/routers/teams.py` declares `PATCH /agents/{agent_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /projects/{project_id}
`backend/app/routers/projects.py` declares `PATCH /projects/{project_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /teams/{team_id}
`backend/app/routers/teams.py` declares `PATCH /teams/{team_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 /notifications/read-all
`backend/app/routers/realtime.py` declares `POST /notifications/read-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /notifications/{notif_id}/read
`backend/app/routers/realtime.py` declares `POST /notifications/{notif_id}/read` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /projects
`backend/app/routers/projects.py` declares `POST /projects` 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 /projects/{project_id}/chat
`backend/app/routers/chat.py` declares `POST /projects/{project_id}/chat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /projects/{project_id}/context
`backend/app/routers/context.py` declares `POST /projects/{project_id}/context` 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 /projects/{project_id}/edges
`backend/app/routers/edges.py` declares `POST /projects/{project_id}/edges` 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 /projects/{project_id}/pause
`backend/app/routers/projects.py` declares `POST /projects/{project_id}/pause` 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 /projects/{project_id}/resume
`backend/app/routers/projects.py` declares `POST /projects/{project_id}/resume` 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 /projects/{project_id}/teams
`backend/app/routers/teams.py` declares `POST /projects/{project_id}/teams` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /tasks/{task_id}/continue
`backend/app/routers/tasks.py` declares `POST /tasks/{task_id}/continue` 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 /tasks/{task_id}/stop
`backend/app/routers/tasks.py` declares `POST /tasks/{task_id}/stop` 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 /teams/{team_id}/agents
`backend/app/routers/teams.py` declares `POST /teams/{team_id}/agents` 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 /agents/{agent_id}/memory
`backend/app/routers/memory.py` declares `PUT /agents/{agent_id}/memory` 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: claude-design-handoff/marketing/support.js (1466 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: claude-design-handoff/product/support.js (1466 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/a900528f-51df-42c9-b0cc-70805a95e978/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a900528f-51df-42c9-b0cc-70805a95e978/

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.