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

Sujai06062011/pra-backend-meta

https://github.com/Sujai06062011/pra-backend-meta · scanned 2026-06-16 00:25 UTC (2 months, 2 weeks ago)

118 raw signals (0 security + 118 graph)

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

Complete repo analysis

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

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

Showing 109 of 112 actionable findings. 118 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 `deactivate_medicine` without auth dependency — main.py:408
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:408 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_availability` without auth dependency — routers/availability.py:372
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/availability.py:372 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_schedule_day` without auth dependency — routers/schedule.py:98
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/schedule.py:98 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `answer_query` without auth dependency — main.py:1833
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1833 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `increment_usage` without auth dependency — main.py:402
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:402 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_appointment_status` without auth dependency — main.py:1106
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1106 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_config` without auth dependency — main.py:607
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:607 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_doctor` without auth dependency — main.py:1895
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1895 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_patient` without auth dependency — main.py:922
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:922 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_medicine` without auth dependency — main.py:371
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:371 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `block_from_cancel` without auth dependency — routers/availability.py:389
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/availability.py:389 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `book_appointment` without auth dependency — main.py:2032
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:2032 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bulk_cancel_appointments` without auth dependency — main.py:1209
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1209 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_prescription_v2` without auth dependency — main.py:1581
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1581 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_visit` without auth dependency — main.py:949
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:949 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mark_no_show` without auth dependency — main.py:1114
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1114 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `meta_webhook_inbound` without auth dependency — main.py:235
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:235 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `onboard_clinic` without auth dependency — main.py:62
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:62 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `queue_next` without auth dependency — main.py:1358
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1358 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `queue_prev` without auth dependency — main.py:1374
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1374 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `queue_set_token` without auth dependency — main.py:1391
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1391 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reload_scheduler_endpoint` without auth dependency — main.py:646
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:646 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_visit_vitals` without auth dependency — main.py:988
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:988 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `send_prescription_whatsapp` without auth dependency — main.py:1695
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1695 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_availability` without auth dependency — routers/availability.py:332
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/availability.py:332 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_schedule_day` without auth dependency — routers/schedule.py:73
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/schedule.py:73 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `test_meta_interactive` without auth dependency — main.py:2154
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:2154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_evening_reminders` without auth dependency — main.py:330
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:330 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_followup_calls` without auth dependency — main.py:1927
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1927 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_followup_whatsapp` without auth dependency — main.py:1920
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1920 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_morning_reminders` without auth dependency — main.py:323
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:323 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_review_requests` without auth dependency — main.py:344
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:344 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_visit_summary` without auth dependency — main.py:337
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:337 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `voice_followup_response` without auth dependency — main.py:1912
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1912 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `voice_followup` without auth dependency — main.py:1905
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1905 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `whatsapp_webhook` without auth dependency — main.py:188
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:188 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `whatsapp_webhook` without auth dependency — main_working.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.
main_working.py:42 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `write_prescription` without auth dependency — main.py:417
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:417 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_clinic_schedule` without auth dependency — routers/clinic_schedule.py:106
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
routers/clinic_schedule.py:106 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_medicine` without auth dependency — main.py:386
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:386 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_prescription` without auth dependency — main.py:1428
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
main.py:1428 securityAuth fastapi unauth mutation
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 data Coverage conf 1.00 ORM models found but no DB engine detected
The repo defines tables/models but no DB connection string was found. Likely lives in env vars or a config file the scanner didn't read.
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 13 source file(s) (ratio 0.08). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 195 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 quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: database.py:get_patient_by_mobile, database.py:get_patient_by_mobile 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.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: main.py:med_line, main.py:med_line, main.py:med_line 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 quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `create_prescription_v2` in main.py:1582
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: build_date_options
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
whatsapp_handler.py:133
low System graph software Dead code conf 1.00 Possibly dead Python function: check_holiday
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
database.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: make_followup_call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
followup.py:347
low System graph software Dead code conf 1.00 Possibly dead Python function: send_followup_whatsapp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
followup.py:314
low System graph software Dead code conf 1.00 Possibly dead Python function: send_meta_template
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
main.py:142
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 /medicines/{medicine_id}
`main.py` declares `DELETE /medicines/{medicine_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 /
`main_working.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 /appointments
`main.py` declares `GET /appointments` 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 /appointments/today
`main.py` declares `GET /appointments/today` 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 /config/{doctor_id}
`main.py` declares `GET /config/{doctor_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 /dashboard/stats
`main.py` declares `GET /dashboard/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 /followups/pending
`main.py` declares `GET /followups/pending` 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 /medicines
`main.py` declares `GET /medicines` 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 /medicines/categories
`main.py` declares `GET /medicines/categories` 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 /patients
`main.py` declares `GET /patients` 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 /patients/family/{head_mobile}
`main.py` declares `GET /patients/family/{head_mobile}` 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 /patients/lookup
`main.py` declares `GET /patients/lookup` 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 /patients/search
`main.py` declares `GET /patients/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /patients/{patient_id}
`main.py` declares `GET /patients/{patient_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 /patients/{patient_id}/visits
`main.py` declares `GET /patients/{patient_id}/visits` 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 /patients/{patient_id}/vitals-history
`main.py` declares `GET /patients/{patient_id}/vitals-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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /prescriptions
`main.py` declares `GET /prescriptions` 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 /prescriptions/active
`main.py` declares `GET /prescriptions/active` 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 /prescriptions/{prescription_id}/detail
`main.py` declares `GET /prescriptions/{prescription_id}/detail` 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 /privacy
`main.py` declares `GET /privacy` 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 /queue/status
`main.py` declares `GET /queue/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /visits/{visit_id}/vitals
`main.py` declares `GET /visits/{visit_id}/vitals` 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 /webhook/meta
`main.py` declares `GET /webhook/meta` 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 /webhook/whatsapp
`main_working.py` declares `GET /webhook/whatsapp` 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 /appointments/{appointment_id}/status
`main.py` declares `PATCH /appointments/{appointment_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: PATCH /config/{doctor_id}/{config_key}
`main.py` declares `PATCH /config/{doctor_id}/{config_key}` 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 /medicines/{medicine_id}/increment-usage
`main.py` declares `PATCH /medicines/{medicine_id}/increment-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: PATCH /patients/{patient_id}
`main.py` declares `PATCH /patients/{patient_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 /admin/onboard-clinic
`main.py` declares `POST /admin/onboard-clinic` 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 /appointments/bulk-cancel
`main.py` declares `POST /appointments/bulk-cancel` 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 /appointments/{appointment_id}/no-show
`main.py` declares `POST /appointments/{appointment_id}/no-show` 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 /config/reload-scheduler
`main.py` declares `POST /config/reload-scheduler` 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 /medicines
`main.py` declares `POST /medicines` 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 /patients/register
`main.py` declares `POST /patients/register` 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 /prescriptions
`main.py` declares `POST /prescriptions` 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 /prescriptions/write
`main.py` declares `POST /prescriptions/write` 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 /prescriptions/{prescription_id}/send-whatsapp
`main.py` declares `POST /prescriptions/{prescription_id}/send-whatsapp` 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 /queue/next
`main.py` declares `POST /queue/next` 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 /queue/prev
`main.py` declares `POST /queue/prev` 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 /queue/set-token
`main.py` declares `POST /queue/set-token` 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 /trigger/evening-reminders
`main.py` declares `POST /trigger/evening-reminders` 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 /trigger/morning-reminders
`main.py` declares `POST /trigger/morning-reminders` 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 /trigger/review-requests
`main.py` declares `POST /trigger/review-requests` 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 /trigger/visit-summary
`main.py` declares `POST /trigger/visit-summary` 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 /visits
`main.py` declares `POST /visits` 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 /visits/{visit_id}/vitals
`main.py` declares `POST /visits/{visit_id}/vitals` 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 /webhook/meta
`main.py` declares `POST /webhook/meta` 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 /webhook/whatsapp
`main_working.py` declares `POST /webhook/whatsapp` 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 /medicines/{medicine_id}
`main.py` declares `PUT /medicines/{medicine_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 /prescriptions/{prescription_id}
`main.py` declares `PUT /prescriptions/{prescription_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: main.py (2168 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/8eadf990-1c08-48b2-8b2a-58deb883dde1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8eadf990-1c08-48b2-8b2a-58deb883dde1/

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.