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

Qteneqja/Nurse-Triage-Assistant

https://github.com/Qteneqja/Nurse-Triage-Assistant · scanned 2026-06-15 23:43 UTC (2 months, 4 weeks ago)

192 raw signals (19 security + 173 graph)

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

Complete repo analysis

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

JSON
Combined
65.7
/100
Security checks
66
7 findings
System graph
66
100.0% cov · 153 findings
Critical
2
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 2 High 12 Medium 12 Low 127 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 153 Crowd 0 Layer: Quality 69 Security 13 Software 20 Hardware 2 Frontend 1 Cicd 3 Api 52
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 65.7/100 with 100.0% coverage. It contains 3034 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 173 findings — concentrated in quality (74), api (52), software (20). Risk profile is high: 0 critical, 9 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 152 of 160 actionable findings. 283 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.

critical Security checks quality Practices conf 0.82 7 occurrences Foundry mined mock as real or placeholder: Qteneqja/Nurse-Triage-Assistant
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
7 occurrences
repo-level (7 hits)
critical Security checks security auth conf 0.78 11 occurrences Foundry mined security auth guardrail gaps: Qteneqja/Nurse-Triage-Assistant
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
11 occurrences
repo-level (11 hits)
high Security checks quality Practices conf 0.84 10 occurrences Foundry mined bad chains: Qteneqja/Nurse-Triage-Assistant
Comment chain pattern product: bad_chains Repo: Qteneqja/Nurse-Triage-Assistant Thread: Qteneqja/Nurse-Triage-Assistant#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_rea…
10 occurrences
repo-level (10 hits)
high Security checks quality Quality conf 0.76 3 occurrences Foundry mined schema ui api mismatch: Qteneqja/Nurse-Triage-Assistant
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: weak_supervision_needs_review Repo: Q…
3 occurrences
repo-level (3 hits)
high Security checks quality Testing conf 0.78 24 occurrences Foundry mined test ci gap after feedback: Qteneqja/Nurse-Triage-Assistant
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: weak_supervision_needs_…
24 occurrences
repo-level (24 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin${path} (src/dashboard_static/dashboard.js:23)
`src/dashboard_static/dashboard.js:23` calls `GET /admin${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/dashboard${path} (src/dashboard_static/birchwood.js:30)
`src/dashboard_static/birchwood.js:30` calls `GET /api/v1/dashboard${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/dashboard/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/dashboard/records?limit=1 (src/dashboard_static/login.js:16)
`src/dashboard_static/login.js:16` calls `GET /api/v1/dashboard/records?limit=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/dashboard/records` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_session` without auth dependency — src/api/routes.py:158
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routes.py:158 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `handle_gather` without auth dependency — src/twilio/routes.py:1648
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/twilio/routes.py:1648 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `handle_incoming_call` without auth dependency — src/twilio/routes.py:1426
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/twilio/routes.py:1426 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `handle_thinking` without auth dependency — src/twilio/routes.py:2003
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/twilio/routes.py:2003 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_session` without auth dependency — src/api/routes.py:70
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routes.py:70 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_turn` without auth dependency — src/api/routes.py:92
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/api/routes.py:92 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 47 occurrences Foundry mined assumption checks: Qteneqja/Nurse-Triage-Assistant
Comment chain pattern product: assumption_checks Repo: Qteneqja/Nurse-Triage-Assistant Thread: Qteneqja/Nurse-Triage-Assistant#8 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has…
47 occurrences
repo-level (47 hits)
medium Security checks quality Practices conf 0.70 8 occurrences Foundry mined unresolved feedback: Qteneqja/Nurse-Triage-Assistant
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
8 occurrences
repo-level (8 hits)
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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
gitleaks/gitleaks-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/ci.yml:35
.github/workflows/nurse-triage-api-AutoDeployTrigger-58c15c36-b65d-4acc-a121-a29399dcc40c.yml:23
.github/workflows/secret-scan.yml:37
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/nurse-triage-api-AutoDeployTrigger-58c15c36-b65d-4acc-a121-a29399dcc40c.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/main.py:173
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/main.py:173 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/dashboard_static/birchwood.js:431
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/dashboard_static/birchwood.js:431 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/dashboard_static/dashboard.js:167
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/dashboard_static/dashboard.js:167 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/dashboard_static/dashboard.js:9
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/dashboard_static/dashboard.js:9 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/dashboard_static/login.js:32
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/dashboard_static/login.js:32 Local storage auth token
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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 43 placeholder/mock markers across 15 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 quality Integrity conf 1.00 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_API_KEY`, `GEMMA_API_KEY`, `GEMMA_BASE_URL`, `GITHUB_HEAD_REF`, `GITHUB_REF_NAME`, `GITHUB_SHA`, `LLM_TIMEOUT_SECONDS`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
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 193 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.14-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 17
Dockerfile:2, 17 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 7 locations
.github/workflows/ci.yml:48, 72, 103, 125, 146, 174 (6 hits)
.github/workflows/nurse-triage-api-AutoDeployTrigger-58c15c36-b65d-4acc-a121-a29399dcc40c.yml:20
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/safety/red_flag_rules.py:run_red_flag_rules, src/safety/red_flags.py:score_red_flags 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.
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/security/middleware.py:dispatch, src/security/middleware.py:dispatch, src/security/middleware.py:dispatch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/platform/workflows/spec_workflow.py:start_session, src/verticals/insurance/workflow.py:start_session, src/verticals/automotive_collision/workflow.py:start_session, src/verticals/property_management/workflow.py:start_session This is *the* AI-coder…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: src/platform/workflows/spec_workflow.py:handle_turn, src/verticals/insurance/workflow.py:handle_turn, src/verticals/automotive_collision/workflow.py:handle_turn, src/verticals/healthcare/workflow.py:handle_turn This is *the* AI-coder failure mode (4×…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: src/platform/extraction/base.py:extract, src/platform/extraction/service.py:extract, src/platform/extraction/service.py:extract, src/verticals/insurance/extraction.py:extract This is *the* AI-coder failure mode (4× more duplication in vibe-coded repo…
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 `_extraction_v1` in src/platform/workflows/spec_workflow.py:137
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 `automotive_collision_birchwood_extraction_v1` in src/verticals/automotive_collision/extraction.py:15
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 `automotive_collision_birchwood_rules_v1` in src/verticals/automotive_collision/spec.py:38
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 `automotive_collision_birchwood_rules_v1` in src/verticals/automotive_collision/workflow.py:189
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 `birchwood_collision_intake_v1` in scripts/seed_birchwood_demo.py:37
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 `birchwood_collision_intake_v1` in src/pilot/metrics.py:15
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 `birchwood_collision_intake_v1` in src/twilio/routes.py:500
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 `birchwood_collision_intake_v1` in src/verticals/automotive_collision/constants.py:4
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 `birchwood_collision_intake_v1` in tests/test_birchwood_collision_demo_pack.py:33
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 `birchwood_collision_intake_v1` in tests/test_pilot_metrics.py:22
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 `birchwood_collision_intake_v1` in tests/test_pr4_dashboard_records.py:21
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 `generate_v2` in archive/ml_experiments/scripts/generate_triage_data_v2.py:187
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 `healthcare_triage_extraction_v1` in src/verticals/healthcare/extraction.py:15
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 `healthcare_triage_extraction_v1` in src/verticals/healthcare/schemas.py:13
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 `healthcare_triage_v1` in src/config.py:144
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 `healthcare_triage_v1` in src/platform/organizations/bootstrap.py:70
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 `healthcare_triage_v1` in src/twilio/webhook_stability.py:389
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 `healthcare_triage_v1` in src/verticals/healthcare/constants.py:4
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 `healthcare_triage_v1` in tests/test_birchwood_pitch_dashboard.py:46
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 `healthcare_triage_v1` in tests/test_phase10_bootstrap.py:29
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 `healthcare_triage_v1` in tests/test_phase10_extraction.py:16
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 `healthcare_triage_v1` in tests/test_phase10_routing.py:41
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 `healthcare_triage_v1` in tests/test_phase10_twilio_compatibility.py:18
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 `healthcare_triage_v1` in tests/test_phase11_routing.py:83
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 `healthcare_triage_v1` in tests/test_phase11_twilio_scripted_intake.py:34
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 `healthcare_triage_v1` in tests/test_phase12_dashboard.py:77
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 `healthcare_triage_v1` in tests/test_pr1_runtime_stability.py:52
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 `insurance_claims_fnol_extraction_v1` in src/verticals/insurance/extraction.py:15
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 `insurance_claims_fnol_rules_v1` in src/verticals/insurance/workflow.py:171
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 `insurance_claims_fnol_v1` in src/verticals/insurance/constants.py:4
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 `insurance_claims_fnol_v1` in tests/test_insurance_demo_pack.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 `missing_workflow_v1` in tests/test_phase10_workflows.py:42
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 `model_copy` in scripts/demo_enrichment_local.py:90
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 `model_copy` in tests/test_enrichment_shadow.py:96
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 `noop_v1` in src/platform/extraction/service.py:31
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 `property_maintenance_extraction_v1` in src/verticals/property_management/extraction.py:15
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 `property_maintenance_rules_v1` in src/verticals/property_management/workflow.py:148
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 `property_management_maintenance_v1` in src/verticals/property_management/constants.py:4
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 `sewage_backup` in src/verticals/property_management/rules.py:182
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_assert_canonical_rejects_legacy` in tests/test_canonical_enforcement.py:47
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 `TestLegacyHandoffDeprecated` in tests/test_no_bypass.py:312
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 `towing_followup_v1` in tests/test_pr3_workflow_engine.py:37
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 `triage_sessions_v1` in archive/ml_experiments/train_routing_model_v1.py:12
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 `workflow_spec_v1` in src/platform/workflows/spec.py:25
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: a_measure
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/deepeval_metrics.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: build_case_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/eval_report_writer.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: classify_failures
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/failure_classifier.py:254
low System graph software Dead code conf 1.00 Possibly dead Python function: filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
archive/llm_legacy/client.py:15
low System graph software Dead code conf 1.00 Possibly dead Python function: filter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/safety/phi_masking.py:181
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_twiml_say
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/twilio/routes.py:690
low System graph software Dead code conf 1.00 Possibly dead Python function: health_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
archive/ui_streamlit/api_client.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: infer_vendor_type
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/verticals/property_management/rules.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: is_successful
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/deepeval_metrics.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: narrative_has_segments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/twilio/webhook_stability.py:202
low System graph software Dead code conf 1.00 Possibly dead Python function: require_dashboard_shell_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/api/dashboard.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: require_enrichment_enabled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/api/enrichment_admin.py:27
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_extraction_service
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/platform/extraction/service.py:135
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_retriever
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/protocols/retriever.py:356
low System graph software Dead code conf 1.00 Possibly dead Python function: run_simulated_patient_cases
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/simulated_patient_runner.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: start_cleanup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/storage/memory.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_twilio_signature
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/security/twilio_signature.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: warm_up
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/utils/azure_tts.py:40
low System graph software Dead code conf 1.00 Possibly dead Python function: write_eval_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/evals/eval_report_writer.py:151
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 /{session_id}
`src/api/routes.py` declares `DELETE /{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`src/main.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 /actions
`src/api/dashboard.py` declares `GET /actions` 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 /admin/organizations
`src/api/admin.py` declares `GET /admin/organizations` 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 /admin/sessions
`src/api/admin.py` declares `GET /admin/sessions` 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 /admin/sessions/{session_id}
`src/api/admin.py` declares `GET /admin/sessions/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/sessions/{session_id}/actions
`src/api/admin.py` declares `GET /admin/sessions/{session_id}/actions` 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 /admin/sessions/{session_id}/turns
`src/api/admin.py` declares `GET /admin/sessions/{session_id}/turns` 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 /admin/summary
`src/api/admin.py` declares `GET /admin/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: GET /admin/workflows
`src/api/admin.py` declares `GET /admin/workflows` 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/v1/voice/audio/typing.wav
`src/main.py` declares `GET /api/v1/voice/audio/typing.wav` 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 /birchwood/records
`src/api/dashboard.py` declares `GET /birchwood/records` 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 /calls
`src/api/dashboard.py` declares `GET /calls` 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 /calls/{session_id}
`src/api/dashboard.py` declares `GET /calls/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /calls/{session_id}/extraction
`src/api/dashboard.py` declares `GET /calls/{session_id}/extraction` 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 /calls/{session_id}/final-result
`src/api/dashboard.py` declares `GET /calls/{session_id}/final-result` 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 /calls/{session_id}/turns
`src/api/dashboard.py` declares `GET /calls/{session_id}/turns` 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
`src/api/dashboard.py` declares `GET /dashboard` 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/actions
`src/api/dashboard.py` declares `GET /dashboard/actions` 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/birchwood
`src/api/dashboard.py` declares `GET /dashboard/birchwood` 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/birchwood/records/{session_id}
`src/api/dashboard.py` declares `GET /dashboard/birchwood/records/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/calls
`src/api/dashboard.py` declares `GET /dashboard/calls` 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/calls/{session_id}
`src/api/dashboard.py` declares `GET /dashboard/calls/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/enrichment
`src/api/dashboard.py` declares `GET /dashboard/enrichment` 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/login
`src/api/dashboard.py` declares `GET /dashboard/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: GET /dashboard/records
`src/api/dashboard.py` declares `GET /dashboard/records` 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/records/{session_id}
`src/api/dashboard.py` declares `GET /dashboard/records/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/sessions
`src/api/dashboard.py` declares `GET /dashboard/sessions` 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/sessions/{session_id}
`src/api/dashboard.py` declares `GET /dashboard/sessions/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /insights
`src/api/enrichment_admin.py` declares `GET /insights` 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
`src/main.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 /recent
`src/api/enrichment_admin.py` declares `GET /recent` 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 /records
`src/api/dashboard.py` declares `GET /records` 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 /records/{session_id}
`src/api/dashboard.py` declares `GET /records/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /reports
`src/api/reports.py` declares `GET /reports` 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 /reports/{identifier}
`src/api/reports.py` declares `GET /reports/{identifier}` 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 /sessions/{session_id}
`src/api/enrichment_admin.py` declares `GET /sessions/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /storage-status
`src/api/reports.py` declares `GET /storage-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 /summary
`src/api/dashboard.py` declares `GET /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: GET /{session_id}
`src/api/routes.py` declares `GET /{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/sessions/{session_id}/actions/{action_id}/approve
`src/api/admin.py` declares `POST /admin/sessions/{session_id}/actions/{action_id}/approve` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/sessions/{session_id}/actions/{action_id}/complete
`src/api/admin.py` declares `POST /admin/sessions/{session_id}/actions/{action_id}/complete` 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: POST /admin/sessions/{session_id}/actions/{action_id}/reject
`src/api/admin.py` declares `POST /admin/sessions/{session_id}/actions/{action_id}/reject` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /gather
`src/twilio/routes.py` declares `POST /gather` 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 /incoming
`src/twilio/routes.py` declares `POST /incoming` 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 /records/{session_id}/status
`src/api/dashboard.py` declares `POST /records/{session_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 /start
`src/api/routes.py` declares `POST /start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /thinking
`src/twilio/routes.py` declares `POST /thinking` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{session_id}/turn
`src/api/routes.py` declares `POST /{session_id}/turn` 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: src/orchestrator/orchestrator.py (2127 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/twilio/routes.py (2529 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/279c34d3-ebf4-4dcd-94b6-7603600e7e59/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/279c34d3-ebf4-4dcd-94b6-7603600e7e59/

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.