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.

tkgathr2/security-report-system

https://github.com/tkgathr2/security-report-system · scanned 2026-06-16 00:37 UTC (2 months, 2 weeks ago)

150 raw signals (0 security + 150 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 147 findings

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 0 High 56 Medium 16 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 147 Crowd 0 Layer: Frontend 11 Hardware 1 Security 5 Cicd 1 Quality 23 Api 106

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 65.2/100 with 100.0% coverage. It contains 873 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 150 findings — concentrated in api (106), quality (26), frontend (11). Risk profile is high: 0 critical, 56 high, 19 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 106 of 147 actionable findings. 150 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/auth/admins/${adminId} (frontend/src/App.tsx:275)

`frontend/src/App.tsx:275` calls `DELETE /api/admin/auth/admins/${adminId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/admins/` If this points at an external API, prefix it with `https://` so the m…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/clients/${clientId} (frontend/src/App.tsx:624)

`frontend/src/App.tsx:624` calls `DELETE /api/admin/clients/${clientId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/` If this points at an external API, prefix it with `https://` so the matcher …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/companies/${companyId}/emails/${emailId} (frontend/src/components/CompanyEmailManager.tsx:101)

`frontend/src/components/CompanyEmailManager.tsx:101` calls `DELETE /api/admin/companies/${companyId}/emails/${emailId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/companies//emails/` If this points …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/projects/without-casts (frontend/src/App.tsx:642)

`frontend/src/App.tsx:642` calls `DELETE /api/admin/projects/without-casts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/projects/without-casts` If this points at an external API, prefix it with `https://` s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/reports/${reportId} (frontend/src/App.tsx:930)

`frontend/src/App.tsx:930` calls `DELETE /api/admin/reports/${reportId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/reports/` If this points at an external API, prefix it with `https://` so the matcher …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/staff/${staffId} (frontend/src/App.tsx:724)

`frontend/src/App.tsx:724` calls `DELETE /api/admin/staff/${staffId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff/` If this points at an external API, prefix it with `https://` so the matcher skips…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/auth/access-requests (frontend/src/App.tsx:202)

`frontend/src/App.tsx:202` calls `GET /api/admin/auth/access-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/access-requests` If this points at an external API, prefix it with `https://` so the m…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/auth/admins (frontend/src/App.tsx:213)

`frontend/src/App.tsx:213` calls `GET /api/admin/auth/admins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/admins` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/clients (frontend/src/App.tsx:527)

`frontend/src/App.tsx:527` calls `GET /api/admin/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/companies/${companyId}/emails (frontend/src/components/CompanyEmailManager.tsx:43)

`frontend/src/components/CompanyEmailManager.tsx:43` calls `GET /api/admin/companies/${companyId}/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/companies//emails` If this points at an external API,…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/control-board?date=${encodeURIComponent(date)} (frontend/src/pages/admin/ControlBoardPage.tsx:50)

`frontend/src/pages/admin/ControlBoardPage.tsx:50` calls `GET /api/admin/control-board?date=${encodeURIComponent(date)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/control-board` If this points at an exter…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/csv/imports (frontend/src/App.tsx:484)

`frontend/src/App.tsx:484` calls `GET /api/admin/csv/imports` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/csv/imports` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/csv/imports/${importId}/projects (frontend/src/App.tsx:504)

`frontend/src/App.tsx:504` calls `GET /api/admin/csv/imports/${importId}/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/csv/imports//projects` If this points at an external API, prefix it with `ht…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/email-logs?${params} (frontend/src/pages/admin/EmailLogsPage.tsx:42)

`frontend/src/pages/admin/EmailLogsPage.tsx:42` calls `GET /api/admin/email-logs?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/email-logs` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/inquiries (frontend/src/pages/admin/InquiriesPage.tsx:48)

`frontend/src/pages/admin/InquiriesPage.tsx:48` calls `GET /api/admin/inquiries` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/inquiries` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/me (frontend/src/App.tsx:150)

`frontend/src/App.tsx:150` calls `GET /api/admin/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/me` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/me (frontend/src/pages/RootRedirect.tsx:16)

`frontend/src/pages/RootRedirect.tsx:16` calls `GET /api/admin/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/me` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/projects?date=${dateStr} (frontend/src/App.tsx:338)

`frontend/src/App.tsx:338` calls `GET /api/admin/projects?date=${dateStr}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/projects` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/reports/${reportId}/detail (frontend/src/App.tsx:909)

`frontend/src/App.tsx:909` calls `GET /api/admin/reports/${reportId}/detail` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/reports//detail` If this points at an external API, prefix it with `https://` so t…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/settings/email-notification (frontend/src/pages/admin/DashboardPage.tsx:16)

`frontend/src/pages/admin/DashboardPage.tsx:16` calls `GET /api/admin/settings/email-notification` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/settings/email-notification` If this points at an external API,…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/staff (frontend/src/App.tsx:462)

`frontend/src/App.tsx:462` calls `GET /api/admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/drafts/${uniqueUrl} (frontend/src/pages/FieldReport.tsx:331)

`frontend/src/pages/FieldReport.tsx:331` calls `GET /api/drafts/${uniqueUrl}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/drafts/` If this points at an external API, prefix it with `https://` so the matcher sk…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${uniqueUrl} (frontend/src/pages/FieldReport.tsx:127)

`frontend/src/pages/FieldReport.tsx:127` calls `GET /api/projects/${uniqueUrl}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects/` If this points at an external API, prefix it with `https://` so the matche…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/staff/search?q=${encodeURIComponent(q)} (frontend/src/pages/FieldReport.tsx:1026)

`frontend/src/pages/FieldReport.tsx:1026` calls `GET /api/staff/search?q=${encodeURIComponent(q)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/staff/search` If this points at an external API, prefix it with `http…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/staff/search?q=${encodeURIComponent(query)} (frontend/src/pages/FieldReport.tsx:494)

`frontend/src/pages/FieldReport.tsx:494` calls `GET /api/staff/search?q=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/staff/search` If this points at an external API, prefix it with `h…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/auth/access-requests/${requestId}/approve (frontend/src/App.tsx:224)

`frontend/src/App.tsx:224` calls `POST /api/admin/auth/access-requests/${requestId}/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/access-requests//approve` If this points at an external API, …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/auth/access-requests/${requestId}/reject (frontend/src/App.tsx:246)

`frontend/src/App.tsx:246` calls `POST /api/admin/auth/access-requests/${requestId}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/access-requests//reject` If this points at an external API, pr…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/auth/logout (frontend/src/App.tsx:172)

`frontend/src/App.tsx:172` calls `POST /api/admin/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/auth/request-access (frontend/src/App.tsx:186)

`frontend/src/App.tsx:186` calls `POST /api/admin/auth/request-access` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/request-access` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/clients (frontend/src/App.tsx:596)

`frontend/src/App.tsx:596` calls `POST /api/admin/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/companies/${companyId}/emails (frontend/src/components/CompanyEmailManager.tsx:74)

`frontend/src/components/CompanyEmailManager.tsx:74` calls `POST /api/admin/companies/${companyId}/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/companies//emails` If this points at an external API…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/csv/import (frontend/src/App.tsx:825)

`frontend/src/App.tsx:825` calls `POST /api/admin/csv/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/csv/import` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/email-logs/${logId}/resend (frontend/src/pages/admin/EmailLogsPage.tsx:70)

`frontend/src/pages/admin/EmailLogsPage.tsx:70` calls `POST /api/admin/email-logs/${logId}/resend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/email-logs//resend` If this points at an external API, prefi…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/projects/${cancelModalProject.id}/cancel (frontend/src/App.tsx:361)

`frontend/src/App.tsx:361` calls `POST /api/admin/projects/${cancelModalProject.id}/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/projects//cancel` If this points at an external API, prefix it with…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/projects/${project.id}/cancel/resend (frontend/src/App.tsx:418)

`frontend/src/App.tsx:418` calls `POST /api/admin/projects/${project.id}/cancel/resend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/projects//cancel/resend` If this points at an external API, prefix it w…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/projects/${project.id}/restore (frontend/src/App.tsx:399)

`frontend/src/App.tsx:399` calls `POST /api/admin/projects/${project.id}/restore` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/projects//restore` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/reports/${reportId}/resend (frontend/src/App.tsx:980)

`frontend/src/App.tsx:980` calls `POST /api/admin/reports/${reportId}/resend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/reports//resend` 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 /api/admin/reports/bulk-delete (frontend/src/App.tsx:954)

`frontend/src/App.tsx:954` calls `POST /api/admin/reports/bulk-delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/reports/bulk-delete` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/send-login-url (frontend/src/pages/admin/SendLoginUrlPage.tsx:50)

`frontend/src/pages/admin/SendLoginUrlPage.tsx:50` calls `POST /api/admin/send-login-url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/send-login-url` If this points at an external API, prefix it with `https…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/send-login-url (frontend/src/pages/admin/SendLoginUrlPage.tsx:78)

`frontend/src/pages/admin/SendLoginUrlPage.tsx:78` calls `POST /api/admin/send-login-url` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/send-login-url` If this points at an external API, prefix it with `https…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/staff (frontend/src/App.tsx:667)

`frontend/src/App.tsx:667` calls `POST /api/admin/staff` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/staff/${staffId}/clear-pin (frontend/src/App.tsx:744)

`frontend/src/App.tsx:744` calls `POST /api/admin/staff/${staffId}/clear-pin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff//clear-pin` 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 /api/admin/staff/bulk-clear-pins (frontend/src/App.tsx:769)

`frontend/src/App.tsx:769` calls `POST /api/admin/staff/bulk-clear-pins` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff/bulk-clear-pins` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/staff/import (frontend/src/App.tsx:795)

`frontend/src/App.tsx:795` calls `POST /api/admin/staff/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff/import` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/cast/exchange-cast-token (frontend/src/pages/FieldReport.tsx:215)

`frontend/src/pages/FieldReport.tsx:215` calls `POST /api/cast/exchange-cast-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/cast/exchange-cast-token` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/reports/approve (frontend/src/pages/FieldReport.tsx:435)

`frontend/src/pages/FieldReport.tsx:435` calls `POST /api/reports/approve` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/reports/approve` If this points at an external API, prefix it with `https://` so the matcher …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/staff/register (frontend/src/pages/FieldReport.tsx:1107)

`frontend/src/pages/FieldReport.tsx:1107` calls `POST /api/staff/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/staff/register` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/staff/select (frontend/src/pages/FieldReport.tsx:518)

`frontend/src/pages/FieldReport.tsx:518` calls `POST /api/staff/select` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/staff/select` If this points at an external API, prefix it with `https://` so the matcher skips …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://slack.com/api/files.completeUploadExternal (backend/src/services/notifications.ts:183)

`backend/src/services/notifications.ts:183` calls `POST https://slack.com/api/files.completeUploadExternal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/slack.com/api/files.completeuploadexternal` If this p…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST https://slack.com/api/files.getUploadURLExternal (backend/src/services/notifications.ts:154)

`backend/src/services/notifications.ts:154` calls `POST https://slack.com/api/files.getUploadURLExternal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/slack.com/api/files.getuploadurlexternal` If this point…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/auth/admins/${adminId}/role (frontend/src/App.tsx:258)

`frontend/src/App.tsx:258` calls `PUT /api/admin/auth/admins/${adminId}/role` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/auth/admins//role` If this points at an external API, prefix it with `https://` s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/clients/${editingClient.id} (frontend/src/App.tsx:561)

`frontend/src/App.tsx:561` calls `PUT /api/admin/clients/${editingClient.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/inquiries/${id}/status (frontend/src/pages/admin/InquiriesPage.tsx:66)

`frontend/src/pages/admin/InquiriesPage.tsx:66` calls `PUT /api/admin/inquiries/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/inquiries//status` If this points at an external API, prefix it w…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/settings/email-notification (frontend/src/pages/admin/DashboardPage.tsx:46)

`frontend/src/pages/admin/DashboardPage.tsx:46` calls `PUT /api/admin/settings/email-notification` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/settings/email-notification` If this points at an external API,…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/staff/${editingStaff.id} (frontend/src/App.tsx:697)

`frontend/src/App.tsx:697` calls `PUT /api/admin/staff/${editingStaff.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/staff/` If this points at an external API, prefix it with `https://` so the matcher …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/drafts/${uniqueUrl} (frontend/src/pages/FieldReport.tsx:382)

`frontend/src/pages/FieldReport.tsx:382` calls `PUT /api/drafts/${uniqueUrl}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/drafts/` If this points at an external API, prefix it with `https://` so the matcher sk…

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:companyId/emails/:id

`backend/src/routes/adminCompanyEmails.ts` declares `DELETE /:companyId/emails/: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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /

`backend/src/routes/adminControlBoard.ts` 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 /:companyId/emails

`backend/src/routes/adminCompanyEmails.ts` declares `GET /:companyId/emails` 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 /:project_unique_url

`backend/src/routes/drafts.ts` declares `GET /:project_unique_url` 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 /:reportId/pdf

`backend/src/routes/reports.ts` declares `GET /:reportId/pdf` 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 /google/start

`backend/src/routes/adminAuth.ts` declares `GET /google/start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /imports

`backend/src/routes/adminCsvImport.ts` declares `GET /imports` 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 /imports/:id/projects

`backend/src/routes/adminCsvImport.ts` declares `GET /imports/:id/projects` 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/src/routes/castAuth.ts` 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 /report/:uniqueUrl

`backend/src/index.ts` declares `GET /report/:uniqueUrl` 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 /reset-pin/verify

`backend/src/routes/castAuth.ts` declares `GET /reset-pin/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: GET /search-staff

`backend/src/routes/castAuth.ts` declares `GET /search-staff` 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/src/routes/castAuth.ts` 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: PATCH /:companyId/emails/:emailId

`backend/src/routes/adminCompanyEmails.ts` declares `PATCH /:companyId/emails/:emailId` 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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /:companyId/emails

`backend/src/routes/adminCompanyEmails.ts` declares `POST /:companyId/emails` 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 /:projectId/cancel

`backend/src/routes/adminProjectCancel.ts` declares `POST /:projectId/cancel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /:projectId/cancel/resend

`backend/src/routes/adminProjectCancel.ts` declares `POST /:projectId/cancel/resend` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /:projectId/restore

`backend/src/routes/adminProjectCancel.ts` declares `POST /:projectId/restore` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/test/admin-login

`backend/src/index.ts` declares `POST /api/test/admin-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 /approve

`backend/src/routes/reports.ts` declares `POST /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: POST /exchange-cast-token

`backend/src/routes/castAuth.ts` declares `POST /exchange-cast-token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /field-login

`backend/src/routes/castAuth.ts` declares `POST /field-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 /field-register

`backend/src/routes/castAuth.ts` declares `POST /field-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 /import

`backend/src/routes/adminCsvImport.ts` declares `POST /import` 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 /inquiry

`backend/src/routes/castAuth.ts` declares `POST /inquiry` 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/src/routes/castAuth.ts` 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 /logout

`backend/src/routes/castAuth.ts` declares `POST /logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /magic

`backend/src/routes/castAuth.ts` declares `POST /magic` 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 /magic-link

`backend/src/routes/castAuth.ts` declares `POST /magic-link` 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 /mail-help

`backend/src/routes/castAuth.ts` declares `POST /mail-help` 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/src/routes/castAuth.ts` 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 /reset-pin

`backend/src/routes/castAuth.ts` declares `POST /reset-pin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /reset-pin/confirm

`backend/src/routes/castAuth.ts` declares `POST /reset-pin/confirm` 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 /verify

`backend/src/routes/castAuth.ts` declares `POST /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 /:project_unique_url

`backend/src/routes/drafts.ts` declares `PUT /:project_unique_url` 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/src/index.ts` 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/admin

`backend/src/index.ts` declares `USE /api/admin` 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/admin/auth

`backend/src/index.ts` declares `USE /api/admin/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/admin/companies

`backend/src/index.ts` declares `USE /api/admin/companies` 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/admin/control-board

`backend/src/index.ts` declares `USE /api/admin/control-board` 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/admin/csv

`backend/src/index.ts` declares `USE /api/admin/csv` 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/admin/email-logs

`backend/src/index.ts` declares `USE /api/admin/email-logs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: USE /api/admin/projects

`backend/src/index.ts` declares `USE /api/admin/projects` 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/admin/recipients

`backend/src/index.ts` declares `USE /api/admin/recipients` 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/admin/reports

`backend/src/index.ts` declares `USE /api/admin/reports` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: USE /api/cast

`backend/src/index.ts` declares `USE /api/cast` 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/drafts

`backend/src/index.ts` declares `USE /api/drafts` 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/projects

`backend/src/index.ts` declares `USE /api/projects` 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/reports

`backend/src/index.ts` declares `USE /api/reports` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: USE /api/staff

`backend/src/index.ts` declares `USE /api/staff` 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

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/e45165af-16e8-47a5-a6b3-166e934c4d07/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e45165af-16e8-47a5-a6b3-166e934c4d07/

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.