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

roshannandhu/Udaya_LMS

https://github.com/roshannandhu/Udaya_LMS · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

224 raw signals (0 security + 224 graph)

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

Complete repo analysis

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

JSON
Combined
62.6
/100
Security checks
63
0 findings
System graph
63
100.0% cov · 188 findings
Critical
3
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 3 High 2 Medium 16 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 188 Crowd 0 Layer: Software 29 Frontend 61 Hardware 3 Security 7 Quality 38 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 62.6/100 with 100.0% coverage. It contains 2182 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 224 findings — concentrated in quality (74), frontend (61), api (50). Risk profile is high: 3 critical, 2 high, 37 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 117 of 188 actionable findings. 224 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 System graph security Secrets conf 1.00 Possible secret in frontend/src/store.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/src/store.js:27
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: backend/.env
`backend/.env` looks like a runtime dotenv file. It contains secret-looking assignments for SUPABASE_KEY, SUPABASE_SERVICE_KEY, ZOOM_CLIENT_SECRET, ZOOM_WEBHOOK_SECRET_TOKEN, ZOOM_SDK_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
backend/.env ConfigEnv fileRuntime env
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.local
`frontend/.env.local` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_SUPABASE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
frontend/.env.local ConfigEnv fileRuntime env
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: AGENTS.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
AGENTS.md:63 SecretsAgents md
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:224 SecretsClaude instruction
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/teacher/whatsapp/previewText.jsx:51
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/public/sw.js:54
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/teacher/StudentManageGrid.jsx:59
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api.js:45
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/student/StudentLayout.jsx:36
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/student/StudentProfilePage.jsx:82
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: AGENTS.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 22 occurrences Frontend route `standards` has no Link/navigate to it — frontend/src/App.jsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
22 occurrences
repo-level (22 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/main.py:46
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/main.py:46 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pages/student/StudentVideoPlayerPage.jsx:257
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/pages/student/StudentVideoPlayerPage.jsx:257 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/create_demo_accounts.py:18
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/scripts/backup_db.py:33
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 170 placeholder/mock markers across 38 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 22 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CLOUDFLARE_ACCOUNT_ID`, `CLOUDFLARE_STREAM_API_TOKEN`, `DATABASE_URL`, `ENVIRONMENT`, `GEMINI_API_KEY`, `MODE`, `R2_ACCESS_KEY`, `R2_ACCOUNT_ID` + 14 more. 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 54 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
21 tests / 157 src (ratio 0.13).
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
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: backend/whatsapp.py:section, backend/whatsapp.py:section 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: backend/main.py:fetch_subs, backend/main.py:fetch_subs, backend/main.py:fetch_subs 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.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 39 places
Functions with the same first-5-line body hash: backend/main.py:get_dashboard_stats, backend/main.py:get_dashboard_activity, backend/main.py:create_standard, backend/main.py:update_standard This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hyg…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/whatsapp.py:get_session_state, backend/whatsapp.py:get_session_state, backend/whatsapp.py:get_session_state, backend/whatsapp.py:get_session_state This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.h…
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: backend/whatsapp.py:send_template, backend/whatsapp.py:send_template, backend/whatsapp.py:send_template, backend/whatsapp.py:send_template This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygien…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `get_student_report_v2` in backend/main.py:3014
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_report_image
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/whatsapp.py:711
low System graph software Dead code conf 1.00 Possibly dead Python function: build_report_pdf
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/whatsapp.py:626
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_asg
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1696
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_assignments
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2780
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_att_30
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1993
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_attempts_30
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1996
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_broadcasts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1561
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_class_ids
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1562
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_lc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1698
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_links
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1677
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_live
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1989
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_questions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2020
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_students
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1559
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_studs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1961
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_subjects
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2729
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_subm_30
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1999
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_submissions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2817
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_subs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:7530
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_test_attempts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2024
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_tests
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2776
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_tests_cnt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1695
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_upc_tests
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1699
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_video_progress
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2811
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_videos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:2778
low System graph software Dead code conf 1.00 Possibly dead Python function: login_rate_limit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:1215
low System graph software Dead code conf 1.00 Possibly dead Python function: request_with_retry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:89
low System graph software Dead code conf 1.00 Possibly dead Python function: save_and_insert
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:679
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:987
low System graph software Dead code conf 1.00 Possibly dead Python function: zoom_get_zak
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/main.py:739
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 /api/standards/{standard_id}
`backend/main.py` declares `DELETE /api/standards/{standard_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/students/{student_id}
`backend/main.py` declares `DELETE /api/students/{student_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/subjects/{subject_id}
`backend/main.py` declares `DELETE /api/subjects/{subject_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/me
`backend/main.py` declares `GET /api/auth/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 /api/dashboard/activity
`backend/main.py` declares `GET /api/dashboard/activity` 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/dashboard/insights
`backend/main.py` declares `GET /api/dashboard/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 /api/dashboard/overview
`backend/main.py` declares `GET /api/dashboard/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 /api/dashboard/stats
`backend/main.py` declares `GET /api/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 /api/reports/performance
`backend/main.py` declares `GET /api/reports/performance` 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/reports/standard/{standard_id}/analytics
`backend/main.py` declares `GET /api/reports/standard/{standard_id}/analytics` 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/standards
`backend/main.py` declares `GET /api/standards` 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/standards/{standard_id}
`backend/main.py` declares `GET /api/standards/{standard_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/student/calendar-events
`backend/main.py` declares `GET /api/student/calendar-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 /api/student/whats-new
`backend/main.py` declares `GET /api/student/whats-new` 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/students
`backend/main.py` declares `GET /api/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 /api/students/me/videos
`backend/main.py` declares `GET /api/students/me/videos` 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/students/{student_id}
`backend/main.py` declares `GET /api/students/{student_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/students/{student_id}/password
`backend/main.py` declares `GET /api/students/{student_id}/password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/students/{student_id}/report
`backend/main.py` declares `GET /api/students/{student_id}/report` 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/students/{student_id}/report/v2
`backend/main.py` declares `GET /api/students/{student_id}/report/v2` 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/subjects
`backend/main.py` declares `GET /api/subjects` 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/teacher/thumbnail
`backend/main.py` declares `GET /api/teacher/thumbnail` 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/videos
`backend/main.py` declares `GET /api/videos` 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/videos/{video_id}/viewers
`backend/main.py` declares `GET /api/videos/{video_id}/viewers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/auth/profile
`backend/main.py` declares `PATCH /api/auth/profile` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/standards/{standard_id}
`backend/main.py` declares `PATCH /api/standards/{standard_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/students/me
`backend/main.py` declares `PATCH /api/students/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 /api/students/{student_id}
`backend/main.py` declares `PATCH /api/students/{student_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/students/{student_id}/block
`backend/main.py` declares `PATCH /api/students/{student_id}/block` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/students/{student_id}/unenroll
`backend/main.py` declares `PATCH /api/students/{student_id}/unenroll` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/subjects/{subject_id}
`backend/main.py` declares `PATCH /api/subjects/{subject_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 /api/admin/backfill-student-codes
`backend/main.py` declares `POST /api/admin/backfill-student-codes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/create-student
`backend/main.py` declares `POST /api/admin/create-student` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/change-password
`backend/main.py` declares `POST /api/auth/change-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/login
`backend/main.py` declares `POST /api/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/logout
`backend/main.py` declares `POST /api/auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/refresh
`backend/main.py` declares `POST /api/auth/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/resend-otp
`backend/main.py` declares `POST /api/auth/resend-otp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/verify-device
`backend/main.py` declares `POST /api/auth/verify-device` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/verify-otp
`backend/main.py` declares `POST /api/auth/verify-otp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/standards
`backend/main.py` declares `POST /api/standards` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/student/seen
`backend/main.py` declares `POST /api/student/seen` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/students/me/avatar
`backend/main.py` declares `POST /api/students/me/avatar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/students/{student_id}/reset-password
`backend/main.py` declares `POST /api/students/{student_id}/reset-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/subjects
`backend/main.py` declares `POST /api/subjects` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/teacher/profile-photo
`backend/main.py` declares `POST /api/teacher/profile-photo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/teacher/thumbnail
`backend/main.py` declares `POST /api/teacher/thumbnail` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/videos
`backend/main.py` declares `POST /api/videos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/videos/upload
`backend/main.py` declares `POST /api/videos/upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/videos/youtube
`backend/main.py` declares `POST /api/videos/youtube` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/main.py (11482 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/shared/StudentReportCard.jsx (1655 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: lms-v3_9.jsx (2951 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/e872bc18-bfc2-4b15-8475-bb154056dd4a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e872bc18-bfc2-4b15-8475-bb154056dd4a/

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.