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

SNEKA2107/college-helpdesk-chatbot

https://github.com/SNEKA2107/college-helpdesk-chatbot · scanned 2026-06-16 00:16 UTC (2 months, 2 weeks ago)

278 raw signals (0 security + 278 graph)

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

Complete repo analysis

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

JSON
Combined
62.2
/100
Security checks
62
0 findings
System graph
62
100.0% cov · 269 findings
Critical
10
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 10 High 89 Medium 57 Low 109 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 269 Crowd 0 Layer: Software 3 Frontend 48 Security 55 Cicd 2 Quality 22 Api 139
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.2/100 with 100.0% coverage. It contains 1065 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 278 findings — concentrated in api (139), security (64), frontend (48). Risk profile is high: 19 critical, 89 high, 57 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 259 of 269 actionable findings. 278 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 2 occurrences Possible secret in audit-verify.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 20, 108
audit-verify.js:20, 108 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in audit-warnings.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 10, 14
audit-warnings.js:10, 14 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in backend/create-admin.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/create-admin.js:19
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in backend/dev-local.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 90, 94
backend/dev-local.js:90, 94 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in backend/reset-admin.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/reset-admin.js:9
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in backend/seed.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 40, 52
backend/seed.js:40, 52 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in frontend/src/pages/Register.jsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 48, 49
frontend/src/pages/Register.jsx:48, 49 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /calendar/${id} (frontend/src/pages/admin/CalendarTab.jsx:52)
`frontend/src/pages/admin/CalendarTab.jsx:52` calls `DELETE /calendar/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/calendar/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /events/${ev._id}/register (frontend/src/pages/Events.jsx:27)
`frontend/src/pages/Events.jsx:27` calls `DELETE /events/${ev._id}/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events/<p>/register` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /events/${id} (frontend/src/pages/admin/EventsTab.jsx:42)
`frontend/src/pages/admin/EventsTab.jsx:42` calls `DELETE /events/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /marks/${id} (frontend/src/pages/admin/MarksTab.jsx:48)
`frontend/src/pages/admin/MarksTab.jsx:48` calls `DELETE /marks/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/marks/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /notices/${id} (frontend/src/pages/admin/NoticesTab.jsx:82)
`frontend/src/pages/admin/NoticesTab.jsx:82` calls `DELETE /notices/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices/<p>` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /attendance (frontend/src/pages/Attendance.jsx:15)
`frontend/src/pages/Attendance.jsx:15` calls `GET /attendance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/attendance` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /attendance/summary (frontend/src/pages/Attendance.jsx:14)
`frontend/src/pages/Attendance.jsx:14` calls `GET /attendance/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/attendance/summary` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /attendance/summary?studentId=${encodeURIComponent(id)} (frontend/src/pages/admin/AttendanceTab.jsx:46)
`frontend/src/pages/admin/AttendanceTab.jsx:46` calls `GET /attendance/summary?studentId=${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/attendance/summary` If this points at an ex…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /audit (frontend/src/pages/Admin.jsx:69)
`frontend/src/pages/Admin.jsx:69` calls `GET /audit` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/audit` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/me (app.js:352)
`app.js:352` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/me (frontend/src/pages/admin/AccountTab.jsx:20)
`frontend/src/pages/admin/AccountTab.jsx:20` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/me (frontend/src/pages/Profile.jsx:44)
`frontend/src/pages/Profile.jsx:44` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /calendar (frontend/src/pages/admin/CalendarTab.jsx:19)
`frontend/src/pages/admin/CalendarTab.jsx:19` calls `GET /calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/calendar` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /calendar (frontend/src/pages/Calendar.jsx:14)
`frontend/src/pages/Calendar.jsx:14` calls `GET /calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/calendar` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /contact (frontend/src/pages/Admin.jsx:65)
`frontend/src/pages/Admin.jsx:65` calls `GET /contact` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/contact` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /events (frontend/src/pages/Admin.jsx:66)
`frontend/src/pages/Admin.jsx:66` calls `GET /events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /events (frontend/src/pages/Dashboard.jsx:94)
`frontend/src/pages/Dashboard.jsx:94` calls `GET /events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /events (frontend/src/pages/Events.jsx:20)
`frontend/src/pages/Events.jsx:20` calls `GET /events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /exam (frontend/src/pages/Exam.jsx:22)
`frontend/src/pages/Exam.jsx:22` calls `GET /exam` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /exam/all (frontend/src/pages/Admin.jsx:67)
`frontend/src/pages/Admin.jsx:67` calls `GET /exam/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam/all` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /fees (frontend/src/pages/Fees.jsx:18)
`frontend/src/pages/Fees.jsx:18` calls `GET /fees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/fees` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /fees/all (frontend/src/pages/admin/FeesTab.jsx:18)
`frontend/src/pages/admin/FeesTab.jsx:18` calls `GET /fees/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/fees/all` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave (frontend/src/pages/Admin.jsx:62)
`frontend/src/pages/Admin.jsx:62` calls `GET /leave` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave (frontend/src/pages/Leave.jsx:53)
`frontend/src/pages/Leave.jsx:53` calls `GET /leave` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave (frontend/src/pages/Od.jsx:70)
`frontend/src/pages/Od.jsx:70` calls `GET /leave` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave/${id}/document (frontend/src/pages/admin/LeavesTab.jsx:13)
`frontend/src/pages/admin/LeavesTab.jsx:13` calls `GET /leave/${id}/document` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave/<p>/document` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave/${id}/document (frontend/src/pages/Leave.jsx:95)
`frontend/src/pages/Leave.jsx:95` calls `GET /leave/${id}/document` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave/<p>/document` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /leave/${id}/document (frontend/src/pages/Od.jsx:64)
`frontend/src/pages/Od.jsx:64` calls `GET /leave/${id}/document` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave/<p>/document` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /library (frontend/src/pages/Library.jsx:25)
`frontend/src/pages/Library.jsx:25` calls `GET /library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/library` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /library/borrowed (frontend/src/pages/Library.jsx:34)
`frontend/src/pages/Library.jsx:34` calls `GET /library/borrowed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/library/borrowed` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /library?search=${encodeURIComponent(query.trim())} (frontend/src/pages/Library.jsx:39)
`frontend/src/pages/Library.jsx:39` calls `GET /library?search=${encodeURIComponent(query.trim())}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/library` If this points at an external API, prefix it with …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /marks/cgpa (frontend/src/pages/Cgpa.jsx:33)
`frontend/src/pages/Cgpa.jsx:33` calls `GET /marks/cgpa` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/marks/cgpa` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /marks/cgpa?studentId=${encodeURIComponent(sid)} (frontend/src/pages/admin/MarksTab.jsx:23)
`frontend/src/pages/admin/MarksTab.jsx:23` calls `GET /marks/cgpa?studentId=${encodeURIComponent(sid)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/marks/cgpa` If this points at an external API, prefix i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /marks?studentId=${encodeURIComponent(sid)} (frontend/src/pages/admin/MarksTab.jsx:22)
`frontend/src/pages/admin/MarksTab.jsx:22` calls `GET /marks?studentId=${encodeURIComponent(sid)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/marks` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /notices (app.js:295)
`app.js:295` calls `GET /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /notices (frontend/src/hooks/useUnreadNotices.js:12)
`frontend/src/hooks/useUnreadNotices.js:12` calls `GET /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /notices (frontend/src/pages/Admin.jsx:63)
`frontend/src/pages/Admin.jsx:63` calls `GET /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /notices (frontend/src/pages/Dashboard.jsx:93)
`frontend/src/pages/Dashboard.jsx:93` calls `GET /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /notices (frontend/src/pages/Notices.jsx:25)
`frontend/src/pages/Notices.jsx:25` calls `GET /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests (frontend/src/pages/Admin.jsx:61)
`frontend/src/pages/Admin.jsx:61` calls `GET /requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests (frontend/src/pages/Dashboard.jsx:95)
`frontend/src/pages/Dashboard.jsx:95` calls `GET /requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests (frontend/src/pages/Requests.jsx:33)
`frontend/src/pages/Requests.jsx:33` calls `GET /requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests (frontend/src/pages/Status.jsx:45)
`frontend/src/pages/Status.jsx:45` calls `GET /requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests/stats (frontend/src/pages/Dashboard.jsx:92)
`frontend/src/pages/Dashboard.jsx:92` calls `GET /requests/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests/stats` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /requests/stats (frontend/src/pages/Profile.jsx:44)
`frontend/src/pages/Profile.jsx:44` calls `GET /requests/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests/stats` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /students (frontend/src/pages/Admin.jsx:64)
`frontend/src/pages/Admin.jsx:64` calls `GET /students` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/students` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /timetable (frontend/src/pages/Timetable.jsx:22)
`frontend/src/pages/Timetable.jsx:22` calls `GET /timetable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /timetable/all (frontend/src/pages/Admin.jsx:68)
`frontend/src/pages/Admin.jsx:68` calls `GET /timetable/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable/all` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:5000/api/exam (test-phase5.js:124)
`test-phase5.js:124` calls `GET http://localhost:5000/api/exam` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/exam` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:5000/api/fees (test-phase5.js:137)
`test-phase5.js:137` calls `GET http://localhost:5000/api/fees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/fees` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:5000/api/library (test-phase5.js:150)
`test-phase5.js:150` calls `GET http://localhost:5000/api/library` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/library` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:5000/api/library/borrowed (test-phase5.js:164)
`test-phase5.js:164` calls `GET http://localhost:5000/api/library/borrowed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/library/borrowed` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:5000/api/timetable (test-phase5.js:176)
`test-phase5.js:176` calls `GET http://localhost:5000/api/timetable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/timetable` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /attendance/bulk (frontend/src/pages/admin/AttendanceTab.jsx:36)
`frontend/src/pages/admin/AttendanceTab.jsx:36` calls `POST /attendance/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/attendance/bulk` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /calendar (frontend/src/pages/admin/CalendarTab.jsx:34)
`frontend/src/pages/admin/CalendarTab.jsx:34` calls `POST /calendar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/calendar` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /chat (frontend/src/pages/Chat.jsx:65)
`frontend/src/pages/Chat.jsx:65` calls `POST /chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/chat` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /contact (frontend/src/pages/Contact.jsx:45)
`frontend/src/pages/Contact.jsx:45` calls `POST /contact` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/contact` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /events (frontend/src/pages/admin/EventsTab.jsx:27)
`frontend/src/pages/admin/EventsTab.jsx:27` calls `POST /events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /events/${ev._id}/register (frontend/src/pages/Events.jsx:31)
`frontend/src/pages/Events.jsx:31` calls `POST /events/${ev._id}/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/events/<p>/register` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /exam (frontend/src/pages/admin/ExamsTab.jsx:89)
`frontend/src/pages/admin/ExamsTab.jsx:89` calls `POST /exam` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /fees/payment (frontend/src/pages/Fees.jsx:28)
`frontend/src/pages/Fees.jsx:28` calls `POST /fees/payment` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/fees/payment` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /leave (frontend/src/pages/Leave.jsx:73)
`frontend/src/pages/Leave.jsx:73` calls `POST /leave` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /leave (frontend/src/pages/Od.jsx:84)
`frontend/src/pages/Od.jsx:84` calls `POST /leave` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /marks (frontend/src/pages/admin/MarksTab.jsx:33)
`frontend/src/pages/admin/MarksTab.jsx:33` calls `POST /marks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/marks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /notices (frontend/src/pages/admin/NoticesTab.jsx:61)
`frontend/src/pages/admin/NoticesTab.jsx:61` calls `POST /notices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /requests (frontend/src/pages/Requests.jsx:43)
`frontend/src/pages/Requests.jsx:43` calls `POST /requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /timetable (frontend/src/pages/admin/TimetableTab.jsx:66)
`frontend/src/pages/admin/TimetableTab.jsx:66` calls `POST /timetable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:5000/api/auth/login (audit-warnings.js:12)
`audit-warnings.js:12` calls `POST http://localhost:5000/api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/auth/login` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:5000/api/auth/login (audit-warnings.js:8)
`audit-warnings.js:8` calls `POST http://localhost:5000/api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:5000/api/auth/login` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://college-helpdesk-chatbot-l4bk.onrender.com/api/auth/login (audit-device-retest.js:99)
`audit-device-retest.js:99` calls `POST https://college-helpdesk-chatbot-l4bk.onrender.com/api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/college-helpdesk-chatbot-l4bk.onrender.com/api/auth/lo…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/change-password (frontend/src/pages/admin/AccountTab.jsx:49)
`frontend/src/pages/admin/AccountTab.jsx:49` calls `PUT /auth/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/change-password` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/change-password (frontend/src/pages/Profile.jsx:144)
`frontend/src/pages/Profile.jsx:144` calls `PUT /auth/change-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/change-password` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/profile (frontend/src/pages/admin/AccountTab.jsx:32)
`frontend/src/pages/admin/AccountTab.jsx:32` calls `PUT /auth/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/profile` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/profile (frontend/src/pages/Profile.jsx:102)
`frontend/src/pages/Profile.jsx:102` calls `PUT /auth/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/profile` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/profile (frontend/src/pages/Profile.jsx:126)
`frontend/src/pages/Profile.jsx:126` calls `PUT /auth/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/profile` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /auth/profile (frontend/src/pages/Profile.jsx:83)
`frontend/src/pages/Profile.jsx:83` calls `PUT /auth/profile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/profile` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /calendar/${editId} (frontend/src/pages/admin/CalendarTab.jsx:33)
`frontend/src/pages/admin/CalendarTab.jsx:33` calls `PUT /calendar/${editId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/calendar/<p>` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /contact/${id}/resolve (frontend/src/pages/admin/MessagesTab.jsx:10)
`frontend/src/pages/admin/MessagesTab.jsx:10` calls `PUT /contact/${id}/resolve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/contact/<p>/resolve` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /exam/${selectedId} (frontend/src/pages/admin/ExamsTab.jsx:88)
`frontend/src/pages/admin/ExamsTab.jsx:88` calls `PUT /exam/${selectedId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /exam/${selectedId}/archive (frontend/src/pages/admin/ExamsTab.jsx:106)
`frontend/src/pages/admin/ExamsTab.jsx:106` calls `PUT /exam/${selectedId}/archive` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam/<p>/archive` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /exam/${selectedId}/publish (frontend/src/pages/admin/ExamsTab.jsx:100)
`frontend/src/pages/admin/ExamsTab.jsx:100` calls `PUT /exam/${selectedId}/publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/exam/<p>/publish` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /fees/${feeId}/payments/${index}/verify (frontend/src/pages/admin/FeesTab.jsx:24)
`frontend/src/pages/admin/FeesTab.jsx:24` calls `PUT /fees/${feeId}/payments/${index}/verify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/fees/<p>/payments/<p>/verify` If this points at an external API, …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /leave/${id}/status (frontend/src/pages/admin/LeavesTab.jsx:30)
`frontend/src/pages/admin/LeavesTab.jsx:30` calls `PUT /leave/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/leave/<p>/status` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notices/${notice._id} (frontend/src/pages/admin/NoticesTab.jsx:75)
`frontend/src/pages/admin/NoticesTab.jsx:75` calls `PUT /notices/${notice._id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/notices/<p>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /requests/${id}/status (frontend/src/pages/admin/RequestsTab.jsx:13)
`frontend/src/pages/admin/RequestsTab.jsx:13` calls `PUT /requests/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/requests/<p>/status` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /students/${id}/${action} (frontend/src/pages/admin/StudentsTab.jsx:33)
`frontend/src/pages/admin/StudentsTab.jsx:33` calls `PUT /students/${id}/${action}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/students/<p>/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /timetable/${existingId} (frontend/src/pages/admin/TimetableTab.jsx:65)
`frontend/src/pages/admin/TimetableTab.jsx:65` calls `PUT /timetable/${existingId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /timetable/${existingId}/archive (frontend/src/pages/admin/TimetableTab.jsx:105)
`frontend/src/pages/admin/TimetableTab.jsx:105` calls `PUT /timetable/${existingId}/archive` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable/<p>/archive` If this points at an external API, prefix i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /timetable/${existingId}/publish (frontend/src/pages/admin/TimetableTab.jsx:91)
`frontend/src/pages/admin/TimetableTab.jsx:91` calls `PUT /timetable/${existingId}/publish` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/timetable/<p>/publish` If this points at an external API, prefix it…
Dangling fetchHelper:apicall
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/Chat.jsx:112
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 — audit-device-retest.js:99
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 — audit-device-test.js:168
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 — audit-verify.js:18
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 — audit-warnings.js:8
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 — automated_test/reaudit-live.js:99
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 — sw.js:20
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 — test-phase5.js:124
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 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 quality Integrity conf 1.00 Frontend route `/admin` has no Link/navigate to it — frontend/src/routes/AppRoutes.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.
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/pages/Chat.jsx:112
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/pages/Chat.jsx:112 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin-dashboard.html:165
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-dashboard.html:165 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin-leaves.html:128
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-leaves.html:128 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin-notices.html:143
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-notices.html:143 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin-requests.html:144
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-requests.html:144 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin.html:446
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin.html:446 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app.js:19
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app.js:19 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in attendance.html:93
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
attendance.html:93 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in cgpa.html:81
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
cgpa.html:81 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chat.html:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chat.html:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in contact.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
contact.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:65
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard.html:65 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in events.html:87
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
events.html:87 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in exam.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
exam.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in fees.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
fees.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/pages/Chat.jsx:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/src/pages/Chat.jsx:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:401
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:401 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in leave.html:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
leave.html:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in library.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
library.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in login.html:161
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
login.html:161 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in notices.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
notices.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in od.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
od.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in profile.html:64
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
profile.html:64 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in register.html:152
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
register.html:152 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in requests.html:73
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
requests.html:73 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in selenium_model/html_report.html:509
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
selenium_model/html_report.html:509 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in status.html:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
status.html:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in student-search.html:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
student-search.html:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in timetable.html:80
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
timetable.html:80 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in admin.html:694
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
admin.html:694 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in selenium_model/html_report.html:575
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
selenium_model/html_report.html:575 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in app.js:223
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
app.js:223 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in audit-verify.js:28
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
audit-verify.js:28 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in audit-warnings.js:22
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
audit-warnings.js:22 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/services/auth.js:8
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/services/auth.js:8 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in login.html:319
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
login.html:319 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in register.html:408
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
register.html:408 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in selenium_model/pages/base_page.py:70
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
selenium_model/pages/base_page.py:70 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in verify-css-local.js:13
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
verify-css-local.js:13 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in verify-css.js:9
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
verify-css.js:9 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in verify-mobile.js:9
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
verify-mobile.js:9 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in verify-profile-mobile.js:7
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
verify-profile-mobile.js:7 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — selenium_model/run.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 113 placeholder/mock markers across 34 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 Debug conf 1.00 Debug logging residue appears in source files
Found 411 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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/project-summary.yml:15 CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/Modal.jsx:6
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/pages/admin/StudentsTab.jsx:123
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
24 tests / 140 src (ratio 0.17).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: selenium_model/pages/dashboard_page.py:switch_theme, selenium_model/pages/login_page.py:switch_theme 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'r…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: selenium_model/pages/extra_pages.py:navigate, selenium_model/pages/extra_pages.py:navigate, selenium_model/pages/extra_pages.py:navigate 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 Integrity conf 1.00 Old/deprecated-named symbol `MASTER_TEST_AUDIT_REPORT_backup` in selenium_model/report_generator.py:339
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
backend/package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: inject_auth_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
selenium_model/pages/base_page.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: logout_via_topbar
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
selenium_model/pages/dashboard_page.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: reject_first_leave
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
selenium_model/pages/admin_page.py:99
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-apibase.js:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-device-retest.js:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-device-test.js:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-final-verify.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-verify.js:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — audit-warnings.js:44
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — automated_test/dast_runner.js:121
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — automated_test/reaudit-live.js:4
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/create-admin.js:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/dev-local.js:85
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/export-students.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/migrations/0001-dedupe-attendance.js:66
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/migrations/0002-backfill-fee-verification.js:47
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/migrations/0003-notice-lifecycle.js:61
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/renumber-requests.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/reset-admin.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/cleanup-notices.js:53
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/refresh-demo-data.js:88
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/seed-students.js:144
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/seed.js:32
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/server.js:87
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/test-seq.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/utils/email.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — branding-render.js:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — debug-events.js:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — debug-events2.js:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — debug-live-admin.js:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — debug-login-flow.js:7
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — debug-requests.js:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — generate-icons.js:44
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — screenshot-laptop.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — screenshot-live.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — screenshot-mobile.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-admin-tabs.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-app.js:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-pages.js:35
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-phase3-debug.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-phase3.js:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-phase5.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-react-e2e.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — verify-css-local.js:36
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — verify-css.js:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — verify-dashboard.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — verify-mobile.js:33
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — verify-profile-mobile.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`backend/routes/events.js` declares `DELETE /: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 /:id/register
`backend/routes/events.js` declares `DELETE /:id/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend/routes/library.js` 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 /:id
`backend/routes/students.js` declares `GET /: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 /:id/conflicts
`backend/routes/timetable.js` declares `GET /:id/conflicts` 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 /all
`backend/routes/fees.js` declares `GET /all` 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 /borrowed
`backend/routes/library.js` declares `GET /borrowed` 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 /hours
`backend/routes/library.js` declares `GET /hours` 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
`backend/routes/auth.js` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /pending
`backend/routes/students.js` declares `GET /pending` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /search/:query
`backend/routes/students.js` declares `GET /search/:query` 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 /stats
`backend/routes/requests.js` declares `GET /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 /summary
`backend/routes/attendance.js` 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 /today
`backend/routes/timetable.js` declares `GET /today` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`backend/routes/library.js` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:id/register
`backend/routes/events.js` declares `POST /:id/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bulk
`backend/routes/attendance.js` declares `POST /bulk` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`backend/routes/auth.js` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /payment
`backend/routes/fees.js` declares `POST /payment` 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 /register
`backend/routes/auth.js` declares `POST /register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /renew/:borrowId
`backend/routes/library.js` declares `POST /renew/:borrowId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:feeId/payments/:index/verify
`backend/routes/fees.js` declares `PUT /:feeId/payments/:index/verify` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id
`backend/routes/library.js` declares `PUT /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id/approve
`backend/routes/students.js` declares `PUT /: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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id/archive
`backend/routes/timetable.js` declares `PUT /:id/archive` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id/publish
`backend/routes/timetable.js` declares `PUT /:id/publish` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id/reject
`backend/routes/students.js` declares `PUT /: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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:id/resolve
`backend/routes/contact.js` declares `PUT /:id/resolve` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /change-password
`backend/routes/auth.js` declares `PUT /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: PUT /profile
`backend/routes/auth.js` declares `PUT /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: USE /api
`backend/server.js` declares `USE /api` 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: USE /api/
`backend/server.js` declares `USE /api/` 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: USE /api/attendance
`backend/server.js` declares `USE /api/attendance` 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: USE /api/audit
`backend/server.js` declares `USE /api/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: USE /api/auth
`backend/server.js` declares `USE /api/auth` 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: USE /api/auth/login
`backend/server.js` declares `USE /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: USE /api/auth/register
`backend/server.js` declares `USE /api/auth/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/calendar
`backend/server.js` declares `USE /api/calendar` 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: USE /api/chat
`backend/server.js` declares `USE /api/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: USE /api/contact
`backend/server.js` declares `USE /api/contact` 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: USE /api/events
`backend/server.js` declares `USE /api/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: USE /api/exam
`backend/server.js` declares `USE /api/exam` 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: USE /api/fees
`backend/server.js` declares `USE /api/fees` 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: USE /api/leave
`backend/server.js` declares `USE /api/leave` 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: USE /api/library
`backend/server.js` declares `USE /api/library` 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: USE /api/marks
`backend/server.js` declares `USE /api/marks` 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: USE /api/notices
`backend/server.js` declares `USE /api/notices` 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: USE /api/requests
`backend/server.js` declares `USE /api/requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/students
`backend/server.js` declares `USE /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: USE /api/timetable
`backend/server.js` declares `USE /api/timetable` 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: e2e_test_report.py (1316 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/5b70ed9d-0949-4560-b83e-dfb618224f4a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5b70ed9d-0949-4560-b83e-dfb618224f4a/

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.