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.

RealRogerWinter/onestreamer

https://github.com/RealRogerWinter/onestreamer · scanned 2026-06-15 23:48 UTC (2 months, 3 weeks ago)

441 raw signals (0 security + 441 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 439 actionable findings from 1 signal source. 2 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 · 439 findings

Severity distribution — click a segment to filter

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

Severity: Critical 1 High 33 Medium 59 Low 183 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 439 Crowd 0 Layer: Frontend 120 Hardware 1 Security 37 Cicd 1 Quality 201 Api 79

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 51.7/100 with 100.0% coverage. It contains 4010 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 441 findings — concentrated in quality (202), frontend (120), api (79). Risk profile is high: 1 critical, 33 high, 60 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 79 of 439 actionable findings. 441 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/streambot/messages/${id} (client/src/components/StreamBotManager.tsx:181)

`client/src/components/StreamBotManager.tsx:181` calls `DELETE /api/streambot/messages/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages/` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/viewbot/rotation/status (client/src/components/BotsPanel.tsx:107)

`client/src/components/BotsPanel.tsx:107` calls `GET /admin/viewbot/rotation/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/viewbot/rotation/status` If this points at an external API, prefix it with `h…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/buffs/streamer/current (client/src/components/buffs/BuffDisplay.tsx:227)

`client/src/components/buffs/BuffDisplay.tsx:227` calls `GET /api/buffs/streamer/current` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/buffs/streamer/current` If this points at an external API, prefix it with `htt…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chatbots (client/src/components/BotsPanel.tsx:129)

`client/src/components/BotsPanel.tsx:129` calls `GET /api/chatbots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/chatbots` 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/clips/${clipId}/chat (client/src/components/clips/ClipChatReplay.tsx:38)

`client/src/components/clips/ClipChatReplay.tsx:38` calls `GET /api/clips/${clipId}/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips//chat` If this points at an external API, prefix it with `https://` s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clips/status (client/src/components/mobile/MobileBottomNav.tsx:89)

`client/src/components/mobile/MobileBottomNav.tsx:89` calls `GET /api/clips/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips/status` 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/clips/status (client/src/components/mobile/MobileLandscapeLayout.tsx:308)

`client/src/components/mobile/MobileLandscapeLayout.tsx:308` calls `GET /api/clips/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips/status` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clips/status (client/src/components/stream/TheatreControls.tsx:100)

`client/src/components/stream/TheatreControls.tsx:100` calls `GET /api/clips/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips/status` 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/clips?${params.toString()} (client/src/components/clips/ClipsGallery.tsx:69)

`client/src/components/clips/ClipsGallery.tsx:69` calls `GET /api/clips?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips` 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 /api/soundfx/voices (client/src/components/soundfx/TTSInputModal.tsx:50)

`client/src/components/soundfx/TTSInputModal.tsx:50` calls `GET /api/soundfx/voices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/soundfx/voices` 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 /api/streambot/messages (client/src/components/StreamBotManager.tsx:55)

`client/src/components/StreamBotManager.tsx:55` calls `GET /api/streambot/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages` If this points at an external API, prefix it with `https://` so …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/streambot/settings (client/src/components/StreamBotManager.tsx:42)

`client/src/components/StreamBotManager.tsx:42` calls `GET /api/streambot/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/settings` If this points at an external API, prefix it with `https://` so …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/check-username/${encodeURIComponent(username)} (client/src/components/auth/OAuthUsernameSelection.tsx:79)

`client/src/components/auth/OAuthUsernameSelection.tsx:79` calls `GET /auth/check-username/${encodeURIComponent(username)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/check-username/` If this points at a…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/viewbot/rotation/force (client/src/components/BotsPanel.tsx:213)

`client/src/components/BotsPanel.tsx:213` calls `POST /admin/viewbot/rotation/force` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/viewbot/rotation/force` If this points at an external API, prefix it with `ht…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/bug-reports (client/src/components/BugReportModal.tsx:58)

`client/src/components/BugReportModal.tsx:58` calls `POST /api/bug-reports` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/bug-reports` If this points at an external API, prefix it with `https://` so the matcher ski…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clips/live (client/src/components/clips/ClipCreationModal.tsx:102)

`client/src/components/clips/ClipCreationModal.tsx:102` calls `POST /api/clips/live` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clips/live` 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: POST /api/moderation/ban-chat (client/src/components/user/UserInfoPopup.tsx:140)

`client/src/components/user/UserInfoPopup.tsx:140` calls `POST /api/moderation/ban-chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/moderation/ban-chat` 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/moderation/ban-streamer (client/src/components/user/UserInfoPopup.tsx:206)

`client/src/components/user/UserInfoPopup.tsx:206` calls `POST /api/moderation/ban-streamer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/moderation/ban-streamer` If this points at an external API, prefix it with …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/moderation/timeout (client/src/components/user/UserInfoPopup.tsx:173)

`client/src/components/user/UserInfoPopup.tsx:173` calls `POST /api/moderation/timeout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/moderation/timeout` 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/soundfx/item/soundboard (client/src/components/inventory/inventoryPanel/useInventory.ts:428)

`client/src/components/inventory/inventoryPanel/useInventory.ts:428` calls `POST /api/soundfx/item/soundboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/soundfx/item/soundboard` If this points at an external AP…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/soundfx/item/tts (client/src/components/inventory/inventoryPanel/useInventory.ts:322)

`client/src/components/inventory/inventoryPanel/useInventory.ts:322` calls `POST /api/soundfx/item/tts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/soundfx/item/tts` If this points at an external API, prefix it w…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/streambot/messages (client/src/components/StreamBotManager.tsx:126)

`client/src/components/StreamBotManager.tsx:126` calls `POST /api/streambot/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages` If this points at an external API, prefix it with `https://` s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/streambot/messages/${id}/toggle (client/src/components/StreamBotManager.tsx:202)

`client/src/components/StreamBotManager.tsx:202` calls `POST /api/streambot/messages/${id}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages//toggle` If this points at an external API, pre…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/streambot/messages/reorder (client/src/components/StreamBotManager.tsx:236)

`client/src/components/StreamBotManager.tsx:236` calls `POST /api/streambot/messages/reorder` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages/reorder` If this points at an external API, prefix it w…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/streambot/test (client/src/components/StreamBotManager.tsx:258)

`client/src/components/StreamBotManager.tsx:258` calls `POST /api/streambot/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/test` 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/streambot/toggle (client/src/components/StreamBotManager.tsx:76)

`client/src/components/StreamBotManager.tsx:76` calls `POST /api/streambot/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/toggle` 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: POST /auth/complete-oauth-registration (client/src/components/auth/OAuthUsernameSelection.tsx:120)

`client/src/components/auth/OAuthUsernameSelection.tsx:120` calls `POST /auth/complete-oauth-registration` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/complete-oauth-registration` If this points at an extern…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/streambot/messages/${editingMessage.id} (client/src/components/StreamBotManager.tsx:153)

`client/src/components/StreamBotManager.tsx:153` calls `PUT /api/streambot/messages/${editingMessage.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/messages/` If this points at an external API, pre…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/streambot/settings (client/src/components/StreamBotManager.tsx:100)

`client/src/components/StreamBotManager.tsx:100` calls `PUT /api/streambot/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/streambot/settings` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /users/:userId

`server/routes/admin.js` declares `DELETE /users/:userId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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

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

Unused endpoint

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

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

Unused endpoint

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

`chat-service/api/routes.js` declares `GET /api/moderation` 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 /users

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

Unused endpoint

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

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/remove-timeout

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

Unused endpoint

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

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

Unused endpoint

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

`server/routes/admin-moderation.js` declares `POST /api/admin/unban` 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/ban

`chat-service/api/routes.js` declares `POST /api/ban` 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/remove-timeout

`chat-service/api/routes.js` declares `POST /api/remove-timeout` 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/system-message

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

Unused endpoint

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

`chat-service/api/routes.js` declares `POST /api/timeout` 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/unban

`chat-service/api/routes.js` declares `POST /api/unban` 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 /ban-chat

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /ban-streamer

`server/routes/moderation.js` declares `POST /ban-streamer` 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 /timeout

`server/routes/moderation.js` declares `POST /timeout` 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 /users/:userId/ban

`server/routes/admin.js` declares `POST /users/:userId/ban` 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 /users/:userId/demote-admin

`server/routes/admin.js` declares `POST /users/:userId/demote-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: POST /users/:userId/demote-moderator

`server/routes/admin.js` declares `POST /users/:userId/demote-moderator` 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 /users/:userId/promote-admin

`server/routes/admin.js` declares `POST /users/:userId/promote-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: POST /users/:userId/promote-moderator

`server/routes/admin.js` declares `POST /users/:userId/promote-moderator` 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 /users/:userId/unban

`server/routes/admin.js` declares `POST /users/:userId/unban` 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 /admin

`client/src/setupProxy.js` declares `USE /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 /admin/review

`server/index.js` declares `USE /admin/review` 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

`client/src/setupProxy.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/admin

`server/index.js` 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/audio

`server/index.js` declares `USE /api/audio` 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/buffs

`server/index.js` declares `USE /api/buffs` 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/bug-reports

`server/index.js` declares `USE /api/bug-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/chatbots

`server/index.js` declares `USE /api/chatbots` 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/clips

`server/index.js` declares `USE /api/clips` 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/internal

`server/index.js` declares `USE /api/internal` 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/moderation

`server/index.js` declares `USE /api/moderation` 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/moderation-ai

`server/index.js` declares `USE /api/moderation-ai` 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/random-stream

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

Unused endpoint

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

`server/index.js` declares `USE /api/soundfx` 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/streambot

`server/index.js` declares `USE /api/streambot` 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/turn

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

Unused endpoint

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

`server/index.js` declares `USE /api/tutorial` 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/url-stream

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

Unused endpoint

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

`server/index.js` declares `USE /api/whitelist` 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 /auth

`client/src/setupProxy.js` declares `USE /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 /chat/socket.io

`client/src/setupProxy.js` declares `USE /chat/socket.io` 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 /debug

`client/src/setupProxy.js` declares `USE /debug` 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 /hls

`server/index.js` declares `USE /hls` 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 /socket.io

`client/src/setupProxy.js` declares `USE /socket.io` 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 /uploads

`client/src/setupProxy.js` declares `USE /uploads` 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 /uploads/avatars

`server/index.js` declares `USE /uploads/avatars` 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 /uploads/emojis

`server/index.js` declares `USE /uploads/emojis` 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/dcff9fb9-7ed6-44b6-a77d-e8f0648b8ab7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dcff9fb9-7ed6-44b6-a77d-e8f0648b8ab7/

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.