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

rohansinghdeo123-sys/ai-educator-backend

https://github.com/rohansinghdeo123-sys/ai-educator-backend · scanned 2026-06-15 23:54 UTC (2 months, 3 weeks ago)

96 raw signals (0 security + 96 graph)

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

Complete repo analysis

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

JSON
Combined
83.2
/100
Security checks
83
0 findings
System graph
83
100.0% cov · 82 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 0 Medium 1 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 82 Crowd 0 Layer: Software 15 Hardware 2 Frontend 1 Security 1 Quality 13 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 83.2/100 with 100.0% coverage. It contains 1365 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 96 findings — concentrated in api (50), quality (26), software (15). Risk profile is low: 0 critical, 0 high, 1 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 80 of 82 actionable findings. 96 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.

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
low System graph quality Integrity conf 1.00 57 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_WORKFLOW_VERSION`, `ALLOW_CLIENT_PROGRESS_OVERWRITE`, `AUTO_CREATE_TABLES`, `COACH_BUDGET_ROUTING`, `COACH_DAILY_BUDGET_USD`, `COACH_DEFAULT_INPUT_USD_PER_1M`, `COACH_DEFAULT_OUTPUT_USD_PER_1M`, `COACH_INTERACTION_LIMIT` + 49 more. Add them …
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 hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.10-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 3, 12
Dockerfile:3, 12 (2 hits)
containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
13 tests / 103 src (ratio 0.13).
low System graph quality Integrity conf 1.00 12 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: models.py:accuracy, models.py:accuracy 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.
12 occurrences
repo-level (12 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: Logic/coach/multimodal_learning.py:to_dict, Logic/coach/multimodal_learning.py:to_dict, Logic/coach/multimodal_learning.py:to_dict This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: Logic/section_doubt.py:normalize_mcq_questions, Logic/section_doubt.py:normalize_probable_questions, Logic/agents/exam_agent.py:normalize_structured_mcqs, Logic/agents/exam_agent.py:normalize_probable_questions 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 5 places
Functions with the same first-5-line body hash: routers/coach.py:coach_dashboard, routers/coach.py:coach_daily_learning, routers/progress.py:get_progress, routers/progress.py:analytics This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene)…
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 `agent_runtime_v1` in Logic/agents/coach_agent.py:3036
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: active_versions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
prompts/registry.py:119
low System graph software Dead code conf 1.00 Possibly dead Python function: build_agent_system_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
prompts/prompt_builder.py:217
low System graph software Dead code conf 1.00 Possibly dead Python function: build_mcq_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
prompts/prompt_builder.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: build_memory_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/coach/memory_store.py:6
low System graph software Dead code conf 1.00 Possibly dead Python function: build_probable_questions_prompt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
prompts/prompt_builder.py:158
low System graph software Dead code conf 1.00 Possibly dead Python function: init_db
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
database.py:128
low System graph software Dead code conf 1.00 Possibly dead Python function: persist_event_from_bus
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/observability_store.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: persist_many_events
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/observability_store.py:404
low System graph software Dead code conf 1.00 Possibly dead Python function: privacy_safe_display_name
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/profile_service.py:105
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_charge
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/tools/chemistry_formatter.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_element_number
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/tools/chemistry_formatter.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/security.py:159
low System graph software Dead code conf 1.00 Possibly dead Python function: require_founder_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/security.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: retrieve
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
Logic/coach/retriever.py:133
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_firebase_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/security.py:112
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 /coach/conversations/{user_id}/{conversation_id}
`routers/coach.py` declares `DELETE /coach/conversations/{user_id}/{conversation_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/agent-registry
`routers/admin.py` declares `GET /admin/agent-registry` 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/agents
`routers/admin.py` declares `GET /admin/agents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/agents/{agent_id}
`routers/admin.py` declares `GET /admin/agents/{agent_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/audit
`routers/admin.py` declares `GET /admin/audit` 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/audit-logs
`routers/admin.py` declares `GET /admin/audit-logs` 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/console
`routers/admin.py` declares `GET /admin/console` 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/content/chapters
`routers/admin.py` declares `GET /admin/content/chapters` 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/content/folder-contract
`routers/admin.py` declares `GET /admin/content/folder-contract` 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/content/jobs
`routers/admin.py` declares `GET /admin/content/jobs` 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/content/jobs/{job_id}
`routers/admin.py` declares `GET /admin/content/jobs/{job_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/content/report/{chapter_id}
`routers/admin.py` declares `GET /admin/content/report/{chapter_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/data-registry
`routers/admin.py` declares `GET /admin/data-registry` 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/events
`routers/admin.py` declares `GET /admin/events` 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/me
`routers/admin.py` declares `GET /admin/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/model-registry
`routers/admin.py` declares `GET /admin/model-registry` 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/overview
`routers/admin.py` declares `GET /admin/overview` 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/poll
`routers/admin.py` declares `GET /admin/poll` 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/prompts
`routers/admin.py` declares `GET /admin/prompts` 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/stats
`routers/admin.py` declares `GET /admin/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 /admin/students
`routers/admin.py` declares `GET /admin/students` 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/system-health
`routers/admin.py` declares `GET /admin/system-health` 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/traces
`routers/admin.py` declares `GET /admin/traces` 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 /coach/conversations/{user_id}
`routers/coach.py` declares `GET /coach/conversations/{user_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 /coach/conversations/{user_id}/{conversation_id}
`routers/coach.py` declares `GET /coach/conversations/{user_id}/{conversation_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /coach/{user_id}
`routers/coach.py` declares `GET /coach/{user_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 /get-progress/{user_id}
`routers/progress.py` declares `GET /get-progress/{user_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 /me
`routers/profile.py` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /coach/conversations/{user_id}/{conversation_id}
`routers/coach.py` declares `PATCH /coach/conversations/{user_id}/{conversation_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /me
`routers/profile.py` declares `PATCH /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/action
`routers/admin.py` declares `POST /admin/action` 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/audit
`routers/admin.py` declares `POST /admin/audit` 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/command
`routers/admin.py` declares `POST /admin/command` 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/content/approve/{chapter_id}
`routers/admin.py` declares `POST /admin/content/approve/{chapter_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/content/embed
`routers/admin.py` declares `POST /admin/content/embed` 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/content/generate-json/{chapter_id}
`routers/admin.py` declares `POST /admin/content/generate-json/{chapter_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/content/import-concepts/{chapter_id}
`routers/admin.py` declares `POST /admin/content/import-concepts/{chapter_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/content/ingest-folder
`routers/admin.py` declares `POST /admin/content/ingest-folder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/content/publish/{chapter_id}
`routers/admin.py` declares `POST /admin/content/publish/{chapter_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/message
`routers/admin.py` declares `POST /admin/message` 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 /agent
`routers/agent.py` declares `POST /agent` 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 /coach/autonomous-study/{user_id}
`routers/coach.py` declares `POST /coach/autonomous-study/{user_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 /coach/bootstrap
`routers/coach.py` declares `POST /coach/bootstrap` 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 /coach/chat
`routers/coach.py` declares `POST /coach/chat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /coach/chat/stream
`routers/coach.py` declares `POST /coach/chat/stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /coach/daily-learning/{user_id}
`routers/coach.py` declares `POST /coach/daily-learning/{user_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 /reset-chat
`routers/agent.py` declares `POST /reset-chat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /save-test
`routers/progress.py` declares `POST /save-test` 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 /submit-session
`routers/progress.py` declares `POST /submit-session` 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 /update-progress
`routers/progress.py` declares `POST /update-progress` 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: Logic/agents/coach_agent.py (3273 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/admin_intelligence.py (1360 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_coach_architecture.py (1551 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/4ae90d3b-22c1-4972-b944-119ae984e5a2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4ae90d3b-22c1-4972-b944-119ae984e5a2/

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.