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

ShaoBingGe/doc_api

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

161 raw signals (0 security + 161 graph)

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

Complete repo analysis

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

JSON
Combined
58.9
/100
Security checks
59
0 findings
System graph
59
100.0% cov · 130 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 18 Medium 10 Low 78 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 130 Crowd 0 Layer: Software 8 Frontend 7 Hardware 3 Security 20 Cicd 1 Quality 41 Api 50
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 58.9/100 with 100.0% coverage. It contains 1835 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 161 findings — concentrated in quality (56), api (50), software (24). Risk profile is high: 0 critical, 18 high, 17 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 106 of 130 actionable findings. 161 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` without auth dependency — backend/app/api/v1/conversations.py:71
`@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/api/v1/conversations.py:71 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `activate` without auth dependency — backend/app/ocr_optimizer/router.py:132
`@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/ocr_optimizer/router.py:132 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `_create` without auth dependency — backend/app/api/v1/conversations.py:31
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/conversations.py:31 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `_rollback` without auth dependency — backend/app/api/v1/conversations.py:66
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/conversations.py:66 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `_send_message` without auth dependency — backend/app/api/v1/conversations.py:46
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/conversations.py:46 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `attach_skill` without auth dependency — backend/app/ocr_optimizer/router.py:297
`@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/ocr_optimizer/router.py:297 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_skill` without auth dependency — backend/app/ocr_optimizer/router.py:281
`@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/ocr_optimizer/router.py:281 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_system_admin` without auth dependency — backend/app/api/v1/admin_users.py:42
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/admin_users.py:42 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `extract_document` without auth dependency — backend/app/api/v1/extract.py:25
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/extract.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_init` without auth dependency — backend/app/ocr_optimizer/router.py:82
`@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/ocr_optimizer/router.py:82 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_manual_patch` without auth dependency — backend/app/ocr_optimizer/router.py:234
`@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/ocr_optimizer/router.py:234 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resume_customize_job_endpoint` without auth dependency — backend/app/api/v1/api_defs.py:531
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/v1/api_defs.py:531 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_abort` without auth dependency — backend/app/ocr_optimizer/router.py:220
`@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/ocr_optimizer/router.py:220 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_advance` without auth dependency — backend/app/ocr_optimizer/router.py:181
`@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/ocr_optimizer/router.py:181 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_finalize` without auth dependency — backend/app/ocr_optimizer/router.py:205
`@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/ocr_optimizer/router.py:205 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_optimize` without auth dependency — backend/app/ocr_optimizer/router.py:150
`@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/ocr_optimizer/router.py:150 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `_update_schema` without auth dependency — backend/app/api/v1/conversations.py:56
`@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/api/v1/conversations.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `save_agent` without auth dependency — backend/app/api/v1/reflection_agents.py:64
`@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/api/v1/reflection_agents.py:64 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/api/ApiPreviewPanel.tsx:149
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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.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/launch.json 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 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 quality Integrity conf 1.00 8 occurrences Frontend route `/workspace/api/:apiDefinitionId` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
8 occurrences
repo-level (8 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/api/ApiPreviewPanel.tsx:149
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/api/ApiPreviewPanel.tsx:149 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in prototyype.html:674
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
prototyype.html:674 Direct innerhtml assignment
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 105 placeholder/mock markers across 45 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 frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/components/fields/FieldEditorPanel.tsx:22
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 20 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:1 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
26 tests / 165 src (ratio 0.16).
low System graph quality Integrity conf 1.00 9 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/app/abstractions/storage.py:save, backend/app/abstractions/storage.py:save 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.
9 occurrences
repo-level (9 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/app/processors/mock_processor.py:process_document, backend/app/processors/gemini_processor.py:process_document, backend/app/processors/base.py:process_document, backend/app/processors/piaozone_processor.py:process_document This is *the* AI-co…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `__rename_old` in backend/app/ocr_optimizer/service/customer_iteration.py:1716
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `__rename_old` in backend/tests/test_pending_edits.py:633
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `api_deprecated` in backend/app/core/exceptions.py:65
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `api_deprecated` in backend/app/services/api_definition_service.py:407
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `collapsed_old` in backend/app/services/pending_edits_service.py:121
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_field_rule_of_reads_persisted_copy` in backend/tests/test_field_rule.py:71
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: clear_piaozone_token_cache
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/processors/piaozone_token.py:113
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
backend/alembic/versions/0002_design_v2_compliance.py:54
backend/alembic/versions/a1b2c3d4e5f6_paused_review_skills.py:114
backend/alembic/versions/c5d8a9b1f2e4_country_template_flow.py:40
backend/alembic/versions/d6e9a2b4f1c8_customize_jobs.py:61
backend/alembic/versions/d8d98191e643_add_usage_records.py:44
backend/alembic/versions/e2601813cfca_add_prompt_versions.py:40
backend/alembic/versions/e7d4b91c8a02_promote_global_rules.py:116
backend/alembic/versions/f2c8b3a9d104_add_pending_edits.py:53
low System graph software Dead code conf 1.00 Possibly dead Python function: infer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/services/schema_generator.py:163
low System graph software Dead code conf 1.00 Possibly dead Python function: optimize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ocr_optimizer/service/run_orchestrator.py:446
low System graph software Dead code conf 1.00 Possibly dead Python function: resume_customize_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ocr_optimizer/service/customer_iteration.py:643
low System graph software Dead code conf 1.00 Possibly dead Python function: run_customize_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ocr_optimizer/service/customer_iteration.py:621
low System graph software Dead code conf 1.00 9 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
9 files, 9 locations
backend/alembic/versions/0002_design_v2_compliance.py:25
backend/alembic/versions/a1b2c3d4e5f6_paused_review_skills.py:29
backend/alembic/versions/c5d8a9b1f2e4_country_template_flow.py:30
backend/alembic/versions/d6e9a2b4f1c8_customize_jobs.py:27
backend/alembic/versions/d8d98191e643_add_usage_records.py:22
backend/alembic/versions/e2601813cfca_add_prompt_versions.py:22
backend/alembic/versions/e7d4b91c8a02_promote_global_rules.py:49
backend/alembic/versions/f2c8b3a9d104_add_pending_edits.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_api_def_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/ocr_optimizer/router.py:54
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 /{annotation_id}
`backend/app/api/v1/annotations.py` declares `DELETE /{annotation_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 /{api_def_id}
`backend/app/api/v1/api_defs.py` declares `DELETE /{api_def_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 /{api_def_id}/documents/{document_id}
`backend/app/api/v1/api_defs.py` declares `DELETE /{api_def_id}/documents/{document_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{api_def_id}/pending-edits
`backend/app/api/v1/api_defs.py` declares `DELETE /{api_def_id}/pending-edits` 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 /{conversation_id}
`backend/app/api/v1/conversations.py` declares `DELETE /{conversation_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 /{key_id}
`backend/app/api/v1/api_keys.py` declares `DELETE /{key_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/app/api/v1/api_keys.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 /country-templates
`backend/app/api/v1/platform_templates.py` declares `GET /country-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: GET /golden/{country}/evaluation
`backend/app/api/v1/platform_templates.py` declares `GET /golden/{country}/evaluation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /golden/{country}/seeds
`backend/app/api/v1/platform_templates.py` declares `GET /golden/{country}/seeds` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /golden/{country}/seeds/{seed_id}/file
`backend/app/api/v1/platform_templates.py` declares `GET /golden/{country}/seeds/{seed_id}/file` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me
`backend/app/api/v1/auth.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 /reflection-agents/countries
`backend/app/api/v1/reflection_agents.py` declares `GET /reflection-agents/countries` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reflection-agents/{country}
`backend/app/api/v1/reflection_agents.py` declares `GET /reflection-agents/{country}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users
`backend/app/api/v1/tenant_users.py` declares `GET /users` 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_def_id}
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{api_def_id}/docs
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/docs` 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_def_id}/documents
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/documents` 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_def_id}/pending-edits
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/pending-edits` 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_def_id}/required-fields
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/required-fields` 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_def_id}/samples-review
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/samples-review` 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_def_id}/stats
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/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 /{api_def_id}/versions
`backend/app/api/v1/api_defs.py` declares `GET /{api_def_id}/versions` 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 /{conversation_id}
`backend/app/api/v1/conversations.py` declares `GET /{conversation_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 /{conversation_id}/schema
`backend/app/api/v1/conversations.py` declares `GET /{conversation_id}/schema` 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 /{conversation_id}/schema/history
`backend/app/api/v1/conversations.py` declares `GET /{conversation_id}/schema/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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{template_id}
`backend/app/api/v1/templates.py` declares `GET /{template_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 /batch
`backend/app/api/v1/annotations.py` declares `PATCH /batch` 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 /{annotation_id}
`backend/app/api/v1/annotations.py` declares `PATCH /{annotation_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 /{api_def_id}/status
`backend/app/api/v1/api_defs.py` declares `PATCH /{api_def_id}/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: POST /
`backend/app/api/v1/api_keys.py` declares `POST /` 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 /batch
`backend/app/api/v1/annotations.py` declares `POST /batch` 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 /change-password
`backend/app/api/v1/auth.py` declares `POST /change-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /golden/{country}/evaluate
`backend/app/api/v1/platform_templates.py` declares `POST /golden/{country}/evaluate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`backend/app/api/v1/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 /login/code
`backend/app/api/v1/auth.py` declares `POST /login/code` 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 /users
`backend/app/api/v1/tenant_users.py` declares `POST /users` 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_code}
`backend/app/api/v1/extract.py` declares `POST /{api_code}` 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_def_id}/documents
`backend/app/api/v1/api_defs.py` declares `POST /{api_def_id}/documents` 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_def_id}/pending-edits/commit-draft
`backend/app/api/v1/api_defs.py` declares `POST /{api_def_id}/pending-edits/commit-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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{api_def_id}/samples/{document_id}/confirm-gt
`backend/app/api/v1/api_defs.py` declares `POST /{api_def_id}/samples/{document_id}/confirm-gt` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{api_def_id}/samples/{document_id}/retry-ocr
`backend/app/api/v1/api_defs.py` declares `POST /{api_def_id}/samples/{document_id}/retry-ocr` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{conversation_id}/messages
`backend/app/api/v1/conversations.py` declares `POST /{conversation_id}/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{conversation_id}/rollback/{version}
`backend/app/api/v1/conversations.py` declares `POST /{conversation_id}/rollback/{version}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{key_id}/rotate
`backend/app/api/v1/api_keys.py` declares `POST /{key_id}/rotate` 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 /{template_id}/subscribe
`backend/app/api/v1/templates.py` declares `POST /{template_id}/subscribe` 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 /reflection-agents/{country}/{kind}
`backend/app/api/v1/reflection_agents.py` declares `PUT /reflection-agents/{country}/{kind}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /{api_def_id}
`backend/app/api/v1/api_defs.py` declares `PUT /{api_def_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: PUT /{conversation_id}/schema
`backend/app/api/v1/conversations.py` declares `PUT /{conversation_id}/schema` 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 /{key_id}
`backend/app/api/v1/api_keys.py` declares `PUT /{key_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 quality Complexity conf 1.00 Very large file: backend/app/ocr_optimizer/service/customer_iteration.py (2260 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/workspace-v2/DarkFieldViewer.tsx (2315 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/workspace-v2/OptimizationProcessPanel.tsx (1396 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/stores/workspace-store.ts (1397 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/d8bf4164-2eb8-46eb-b515-67021ec0b4af/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d8bf4164-2eb8-46eb-b515-67021ec0b4af/

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.