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.

quickronserp/Quickrons

https://github.com/quickronserp/Quickrons · scanned 2026-06-15 23:43 UTC (2 months, 4 weeks ago)

152 raw signals (0 security + 152 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 152 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 152 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 50 Medium 9 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 152 Crowd 0 Layer: Frontend 11 Hardware 3 Security 1 Cicd 1 Quality 36 Api 100

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 66.2/100 with 100.0% coverage. It contains 591 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 152 findings — concentrated in api (100), quality (36), frontend (11). Risk profile is high: 0 critical, 50 high, 9 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 100 of 152 actionable findings. 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/v1/partner/menu/${id} (QuickronsApp/src/lib/api.js:234)

`QuickronsApp/src/lib/api.js:234` calls `DELETE /api/v1/partner/menu/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/menu/` If this points at an external API, prefix it with `https://` s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/addresses (QuickronsApp/src/lib/api.js:166)

`QuickronsApp/src/lib/api.js:166` calls `GET /api/v1/addresses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/addresses` If this points at an external API, prefix it with `https://` so the matcher skips…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/analytics (QuickronsApp/src/lib/api.js:305)

`QuickronsApp/src/lib/api.js:305` calls `GET /api/v1/admin/analytics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/analytics` If this points at an external API, prefix it with `https://` so the m…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/orders${qs} (QuickronsApp/src/lib/api.js:302)

`QuickronsApp/src/lib/api.js:302` calls `GET /api/v1/admin/orders${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/orders/` If this points at an external API, prefix it with `https://` so th…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/orders/stuck (QuickronsApp/src/lib/api.js:319)

`QuickronsApp/src/lib/api.js:319` calls `GET /api/v1/admin/orders/stuck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/orders/stuck` If this points at an external API, prefix it with `https://` so…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/partners (QuickronsApp/src/lib/api.js:309)

`QuickronsApp/src/lib/api.js:309` calls `GET /api/v1/admin/partners` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/partners` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/ratings?limit=50 (QuickronsApp/src/lib/api.js:321)

`QuickronsApp/src/lib/api.js:321` calls `GET /api/v1/admin/ratings?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/ratings` If this points at an external API, prefix it with `https://` so …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/riders (QuickronsApp/src/lib/api.js:311)

`QuickronsApp/src/lib/api.js:311` calls `GET /api/v1/admin/riders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/riders` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/admin/wallets (QuickronsApp/src/lib/api.js:307)

`QuickronsApp/src/lib/api.js:307` calls `GET /api/v1/admin/wallets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/wallets` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me (QuickronsApp/src/lib/api.js:127)

`QuickronsApp/src/lib/api.js:127` calls `GET /api/v1/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/kitchens (QuickronsApp/src/lib/api.js:138)

`QuickronsApp/src/lib/api.js:138` calls `GET /api/v1/kitchens` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/kitchens` If this points at an external API, prefix it with `https://` so the matcher skips i…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/kitchens/${id} (QuickronsApp/src/lib/api.js:147)

`QuickronsApp/src/lib/api.js:147` calls `GET /api/v1/kitchens/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/kitchens/` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/kitchens/${id}/menu (QuickronsApp/src/lib/api.js:150)

`QuickronsApp/src/lib/api.js:150` calls `GET /api/v1/kitchens/${id}/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/kitchens//menu` If this points at an external API, prefix it with `https://` so…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/kitchens?q=${encodeURIComponent(q)}&limit=20 (QuickronsApp/src/lib/api.js:144)

`QuickronsApp/src/lib/api.js:144` calls `GET /api/v1/kitchens?q=${encodeURIComponent(q)}&limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/kitchens` If this points at an external API, prefix it wi…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/menu (QuickronsAppV2/src/lib/api.js:53)

`QuickronsAppV2/src/lib/api.js:53` calls `GET /api/v1/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/menu` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/menu?q=${encodeURIComponent(q)}&limit=20 (QuickronsApp/src/lib/api.js:159)

`QuickronsApp/src/lib/api.js:159` calls `GET /api/v1/menu?q=${encodeURIComponent(q)}&limit=20` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/menu` If this points at an external API, prefix it with `http…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/orders/${encodeURIComponent(idOrNumber)} (QuickronsAppV2/src/lib/api.js:63)

`QuickronsAppV2/src/lib/api.js:63` calls `GET /api/v1/orders/${encodeURIComponent(idOrNumber)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders/` If this points at an external API, prefix it wit…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/orders/${id} (QuickronsApp/src/lib/api.js:176)

`QuickronsApp/src/lib/api.js:176` calls `GET /api/v1/orders/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders/` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/partner/me (QuickronsApp/src/lib/api.js:201)

`QuickronsApp/src/lib/api.js:201` calls `GET /api/v1/partner/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/me` If this points at an external API, prefix it with `https://` so the matcher ski…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/partner/menu (QuickronsApp/src/lib/api.js:228)

`QuickronsApp/src/lib/api.js:228` calls `GET /api/v1/partner/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/menu` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/partner/orders${qs} (QuickronsApp/src/lib/api.js:207)

`QuickronsApp/src/lib/api.js:207` calls `GET /api/v1/partner/orders${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/orders/` If this points at an external API, prefix it with `https://` s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/partner/wallet (QuickronsApp/src/lib/api.js:218)

`QuickronsApp/src/lib/api.js:218` calls `GET /api/v1/partner/wallet` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/wallet` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/rider/me (QuickronsApp/src/lib/api.js:278)

`QuickronsApp/src/lib/api.js:278` calls `GET /api/v1/rider/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/me` If this points at an external API, prefix it with `https://` so the matcher skips i…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/rider/me/orders${qs} (QuickronsApp/src/lib/api.js:285)

`QuickronsApp/src/lib/api.js:285` calls `GET /api/v1/rider/me/orders${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/me/orders/` If this points at an external API, prefix it with `https://`…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/rider/orders/available (QuickronsApp/src/lib/api.js:282)

`QuickronsApp/src/lib/api.js:282` calls `GET /api/v1/rider/orders/available` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/orders/available` If this points at an external API, prefix it with `http…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/rider/wallet (QuickronsApp/src/lib/api.js:294)

`QuickronsApp/src/lib/api.js:294` calls `GET /api/v1/rider/wallet` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/wallet` If this points at an external API, prefix it with `https://` so the matcher…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/partner/me (QuickronsApp/src/lib/api.js:204)

`QuickronsApp/src/lib/api.js:204` calls `PATCH /api/v1/partner/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/me` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/partner/menu/${id} (QuickronsApp/src/lib/api.js:232)

`QuickronsApp/src/lib/api.js:232` calls `PATCH /api/v1/partner/menu/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/menu/` If this points at an external API, prefix it with `https://` so…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/admin/orders/${id}/cancel (QuickronsApp/src/lib/api.js:313)

`QuickronsApp/src/lib/api.js:313` calls `POST /api/v1/admin/orders/${id}/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/orders//cancel` If this points at an external API, prefix it with …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/admin/orders/${id}/payment/mark-paid (QuickronsApp/src/lib/api.js:315)

`QuickronsApp/src/lib/api.js:315` calls `POST /api/v1/admin/orders/${id}/payment/mark-paid` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/orders//payment/mark-paid` If this points at an externa…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/admin/orders/${id}/payment/reject (QuickronsApp/src/lib/api.js:317)

`QuickronsApp/src/lib/api.js:317` calls `POST /api/v1/admin/orders/${id}/payment/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/admin/orders//payment/reject` If this points at an external API,…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/send-otp (QuickronsApp/src/lib/api.js:119)

`QuickronsApp/src/lib/api.js:119` calls `POST /api/v1/auth/send-otp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/auth/send-otp` If this points at an external API, prefix it with `https://` so the matc…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/send-otp (QuickronsAppV2/src/lib/api.js:45)

`QuickronsAppV2/src/lib/api.js:45` calls `POST /api/v1/auth/send-otp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/auth/send-otp` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/verify-otp (QuickronsApp/src/lib/api.js:122)

`QuickronsApp/src/lib/api.js:122` calls `POST /api/v1/auth/verify-otp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/auth/verify-otp` If this points at an external API, prefix it with `https://` so the …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/verify-otp (QuickronsAppV2/src/lib/api.js:48)

`QuickronsAppV2/src/lib/api.js:48` calls `POST /api/v1/auth/verify-otp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/auth/verify-otp` If this points at an external API, prefix it with `https://` so the…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders (QuickronsApp/src/lib/api.js:173)

`QuickronsApp/src/lib/api.js:173` calls `POST /api/v1/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders (QuickronsAppV2/src/lib/api.js:57)

`QuickronsAppV2/src/lib/api.js:57` calls `POST /api/v1/orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders/${id}/contact (QuickronsApp/src/lib/api.js:194)

`QuickronsApp/src/lib/api.js:194` calls `POST /api/v1/orders/${id}/contact` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders//contact` If this points at an external API, prefix it with `https://`…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders/${id}/rating (QuickronsApp/src/lib/api.js:188)

`QuickronsApp/src/lib/api.js:188` calls `POST /api/v1/orders/${id}/rating` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/orders//rating` If this points at an external API, prefix it with `https://` s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partner/menu (QuickronsApp/src/lib/api.js:230)

`QuickronsApp/src/lib/api.js:230` calls `POST /api/v1/partner/menu` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/menu` If this points at an external API, prefix it with `https://` so the matche…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partner/orders/${id}/accept (QuickronsApp/src/lib/api.js:210)

`QuickronsApp/src/lib/api.js:210` calls `POST /api/v1/partner/orders/${id}/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/orders//accept` If this points at an external API, prefix it w…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partner/orders/${id}/preparing (QuickronsApp/src/lib/api.js:214)

`QuickronsApp/src/lib/api.js:214` calls `POST /api/v1/partner/orders/${id}/preparing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/orders//preparing` If this points at an external API, prefi…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partner/orders/${id}/ready (QuickronsApp/src/lib/api.js:216)

`QuickronsApp/src/lib/api.js:216` calls `POST /api/v1/partner/orders/${id}/ready` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/orders//ready` If this points at an external API, prefix it wit…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partner/orders/${id}/reject (QuickronsApp/src/lib/api.js:212)

`QuickronsApp/src/lib/api.js:212` calls `POST /api/v1/partner/orders/${id}/reject` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partner/orders//reject` If this points at an external API, prefix it w…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/partners/apply (QuickronsAppV2/src/lib/api.js:73)

`QuickronsAppV2/src/lib/api.js:73` calls `POST /api/v1/partners/apply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/partners/apply` If this points at an external API, prefix it with `https://` so the m…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/rider/me/online (QuickronsApp/src/lib/api.js:280)

`QuickronsApp/src/lib/api.js:280` calls `POST /api/v1/rider/me/online` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/me/online` If this points at an external API, prefix it with `https://` so the …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/rider/orders/${id}/accept (QuickronsApp/src/lib/api.js:288)

`QuickronsApp/src/lib/api.js:288` calls `POST /api/v1/rider/orders/${id}/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/orders//accept` If this points at an external API, prefix it with …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/rider/orders/${id}/delivered (QuickronsApp/src/lib/api.js:292)

`QuickronsApp/src/lib/api.js:292` calls `POST /api/v1/rider/orders/${id}/delivered` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/orders//delivered` If this points at an external API, prefix it…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/rider/orders/${id}/picked-up (QuickronsApp/src/lib/api.js:290)

`QuickronsApp/src/lib/api.js:290` calls `POST /api/v1/rider/orders/${id}/picked-up` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/rider/orders//picked-up` If this points at an external API, prefix it…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/riders/apply (QuickronsAppV2/src/lib/api.js:67)

`QuickronsAppV2/src/lib/api.js:67` calls `POST /api/v1/riders/apply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/v1/riders/apply` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchHelper:request

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

`backend/src/routes/orders.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/src/routes/orders.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 /admin

`backend/src/middleware/auth.js` declares `GET /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: GET /analytics

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

Unused endpoint

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

`backend/src/routes/partners.js` declares `GET /applications` 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 /featured

`backend/src/routes/menu.js` declares `GET /featured` 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/customers.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 /me/orders

`backend/src/routes/customers.js` declares `GET /me/orders` 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 /menu

`backend/src/routes/partner.js` declares `GET /menu` 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 /orders

`backend/src/routes/admin.js` declares `GET /orders` 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 /orders/:id

`backend/src/routes/admin.js` declares `GET /orders/: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 /orders/stuck

`backend/src/routes/admin.js` declares `GET /orders/stuck` 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 /partners

`backend/src/routes/admin.js` declares `GET /partners` 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 /protected

`backend/src/middleware/auth.js` declares `GET /protected` 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 /ratings

`backend/src/routes/admin.js` declares `GET /ratings` 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 /riders

`backend/src/routes/admin.js` declares `GET /riders` 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 /wallets

`backend/src/routes/admin.js` declares `GET /wallets` 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 /me

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

Unused endpoint

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

`backend/src/routes/orders.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/cancel

`backend/src/routes/orders.js` declares `POST /:id/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 /:id/contact

`backend/src/routes/orders.js` declares `POST /:id/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: POST /:id/rating

`backend/src/routes/orders.js` declares `POST /:id/rating` 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/status

`backend/src/routes/orders.js` declares `POST /:id/status` 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 /applications/:id/status

`backend/src/routes/partners.js` declares `POST /applications/:id/status` 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 /apply

`backend/src/routes/partners.js` declares `POST /apply` 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 /menu/upload

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

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /orders/:id/accept

`backend/src/routes/partner.js` declares `POST /orders/:id/accept` 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 /orders/:id/assign-rider

`backend/src/routes/admin.js` declares `POST /orders/:id/assign-rider` 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 /orders/:id/cancel

`backend/src/routes/admin.js` declares `POST /orders/:id/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 /orders/:id/payment/mark-paid

`backend/src/routes/admin.js` declares `POST /orders/:id/payment/mark-paid` 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 /orders/:id/payment/reject

`backend/src/routes/admin.js` declares `POST /orders/:id/payment/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: POST /orders/:id/preparing

`backend/src/routes/partner.js` declares `POST /orders/:id/preparing` 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 /orders/:id/ready

`backend/src/routes/partner.js` declares `POST /orders/:id/ready` 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 /orders/:id/reject

`backend/src/routes/partner.js` declares `POST /orders/: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: POST /partners/:id/suspend

`backend/src/routes/admin.js` declares `POST /partners/:id/suspend` 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 /riders/:id/suspend

`backend/src/routes/admin.js` declares `POST /riders/:id/suspend` 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 /upload

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

Unused endpoint

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

`backend/src/index.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 /api/v1/addresses

`backend/src/index.js` declares `USE /api/v1/addresses` 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/v1/admin

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

`backend/src/index.js` declares `USE /api/v1/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/v1/customers

`backend/src/index.js` declares `USE /api/v1/customers` 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/v1/kitchens

`backend/src/index.js` declares `USE /api/v1/kitchens` 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/v1/menu

`backend/src/index.js` declares `USE /api/v1/menu` 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/v1/orders

`backend/src/index.js` declares `USE /api/v1/orders` 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/v1/partner

`backend/src/index.js` declares `USE /api/v1/partner` 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/v1/partners

`backend/src/index.js` declares `USE /api/v1/partners` 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/v1/rider

`backend/src/index.js` declares `USE /api/v1/rider` 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/v1/riders

`backend/src/index.js` declares `USE /api/v1/riders` 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

`backend/src/index.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

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/d9d122c0-d5df-4192-970e-aed7e4eeb820/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d9d122c0-d5df-4192-970e-aed7e4eeb820/

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.