Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

ankitsrivas14/upload-photobookx

https://github.com/ankitsrivas14/upload-photobookx · scanned 2026-06-17 01:33 UTC (1 month, 2 weeks ago)

246 raw signals (0 security + 246 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -11.7 (diff) · 226 actionable findings from 1 signal source. 20 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
65.0
/100
Security checks
65
0 findings
System graph
65
88.9% cov · 226 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 114 Medium 14 Low 97 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 226 Crowd 0 Layer: Frontend 38 Security 2 Quality 22 Api 164
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.0/100 with 88.9% coverage. It contains 855 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 246 findings — concentrated in api (164), quality (42), frontend (38). Risk profile is high: 0 critical, 114 high, 34 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 225 of 226 actionable findings. 246 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/attendance/hourly-logs/${employeeId}/${dateStr} (frontend/src/services/api.ts:1234)
`frontend/src/services/api.ts:1234` calls `DELETE /api/admin/attendance/hourly-logs/${employeeId}/${dateStr}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/hourly-logs/<p>/<p>` If this poi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/bank-account/categories/${encodeURIComponent(name)} (frontend/src/services/api.ts:921)
`frontend/src/services/api.ts:921` calls `DELETE /api/admin/bank-account/categories/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/categories/<p>` If this poi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/bank-account/narration-rules/${id} (frontend/src/services/api.ts:976)
`frontend/src/services/api.ts:976` calls `DELETE /api/admin/bank-account/narration-rules/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/narration-rules/<p>` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/bank-account/transactions/${id} (frontend/src/services/api.ts:945)
`frontend/src/services/api.ts:945` calls `DELETE /api/admin/bank-account/transactions/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/transactions/<p>` If this points at an external…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/expenses/daily-ad-spend/${entryId} (frontend/src/services/api.ts:687)
`frontend/src/services/api.ts:687` calls `DELETE /api/admin/expenses/daily-ad-spend/${entryId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/daily-ad-spend/<p>` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/expenses/meta-ads/${expenseId} (frontend/src/services/api.ts:645)
`frontend/src/services/api.ts:645` calls `DELETE /api/admin/expenses/meta-ads/${expenseId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/meta-ads/<p>` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/fixed-monthly-expenses/${id} (frontend/src/services/api.ts:898)
`frontend/src/services/api.ts:898` calls `DELETE /api/admin/fixed-monthly-expenses/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/fixed-monthly-expenses/<p>` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/magic-links/${token} (frontend/src/services/api.ts:273)
`frontend/src/services/api.ts:273` calls `DELETE /api/admin/magic-links/${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/magic-links/${token}/delete-images (frontend/src/services/api.ts:318)
`frontend/src/services/api.ts:318` calls `DELETE /api/admin/magic-links/${token}/delete-images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/<p>/delete-images` If this points at an exter…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/pincodes/blocked/${encodeURIComponent(pinCode)} (frontend/src/services/api.ts:1002)
`frontend/src/services/api.ts:1002` calls `DELETE /api/admin/pincodes/blocked/${encodeURIComponent(pinCode)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/blocked/<p>` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/pincodes/cod-added-cities/${encodeURIComponent(city)} (frontend/src/services/api.ts:1338)
`frontend/src/services/api.ts:1338` calls `DELETE /api/admin/pincodes/cod-added-cities/${encodeURIComponent(city)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/cod-added-cities/<p>` If thi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/acknowledge-orders (frontend/src/services/api.ts:441)
`frontend/src/services/api.ts:441` calls `DELETE /api/admin/sales/acknowledge-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/acknowledge-orders` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/ads-performance (frontend/src/services/api.ts:1099)
`frontend/src/services/api.ts:1099` calls `DELETE /api/admin/sales/ads-performance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/ads-performance/${date} (frontend/src/services/api.ts:1103)
`frontend/src/services/api.ts:1103` calls `DELETE /api/admin/sales/ads-performance/${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance/<p>` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/discard-orders (frontend/src/services/api.ts:495)
`frontend/src/services/api.ts:495` calls `DELETE /api/admin/sales/discard-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/discard-orders` If this points at an external API, prefix it with…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/mark-rto (frontend/src/services/api.ts:522)
`frontend/src/services/api.ts:522` calls `DELETE /api/admin/sales/mark-rto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/mark-rto` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/sales/ticket-raised-orders (frontend/src/services/api.ts:468)
`frontend/src/services/api.ts:468` calls `DELETE /api/admin/sales/ticket-raised-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ticket-raised-orders` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/abandoned-checkouts (frontend/src/services/api.ts:1139)
`frontend/src/services/api.ts:1139` calls `GET /api/admin/abandoned-checkouts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/abandoned-checkouts` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/abandoned-checkouts/template (frontend/src/services/api.ts:1143)
`frontend/src/services/api.ts:1143` calls `GET /api/admin/abandoned-checkouts/template` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/abandoned-checkouts/template` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/employees (frontend/src/services/api.ts:1180)
`frontend/src/services/api.ts:1180` calls `GET /api/admin/attendance/employees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/employees` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/employees/stats?month=${month} (frontend/src/services/api.ts:1176)
`frontend/src/services/api.ts:1176` calls `GET /api/admin/attendance/employees/stats?month=${month}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/employees/stats` If this points at an ext…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/hourly-logs/all (frontend/src/services/api.ts:1244)
`frontend/src/services/api.ts:1244` calls `GET /api/admin/attendance/hourly-logs/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/hourly-logs/all` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/hourly-logs/month/${month} (frontend/src/services/api.ts:1240)
`frontend/src/services/api.ts:1240` calls `GET /api/admin/attendance/hourly-logs/month/${month}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/hourly-logs/month/<p>` If this points at an e…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/records/month/${month} (frontend/src/services/api.ts:1202)
`frontend/src/services/api.ts:1202` calls `GET /api/admin/attendance/records/month/${month}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/records/month/<p>` If this points at an external …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/attendance/records?dateStr=${dateStr} (frontend/src/services/api.ts:1198)
`frontend/src/services/api.ts:1198` calls `GET /api/admin/attendance/records?dateStr=${dateStr}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/records` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/auth/me (frontend/src/services/api.ts:247)
`frontend/src/services/api.ts:247` calls `GET /api/admin/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: `/admin/auth/me` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/bank-account/categories (frontend/src/services/api.ts:903)
`frontend/src/services/api.ts:903` calls `GET /api/admin/bank-account/categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/categories` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/bank-account/narration-rules (frontend/src/services/api.ts:965)
`frontend/src/services/api.ts:965` calls `GET /api/admin/bank-account/narration-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/narration-rules` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/bank-account/transactions (frontend/src/services/api.ts:934)
`frontend/src/services/api.ts:934` calls `GET /api/admin/bank-account/transactions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/transactions` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/cogs/configuration/versions (frontend/src/services/api.ts:840)
`frontend/src/services/api.ts:840` calls `GET /api/admin/cogs/configuration/versions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/cogs/configuration/versions` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/expenses/daily-ad-spend (frontend/src/services/api.ts:662)
`frontend/src/services/api.ts:662` calls `GET /api/admin/expenses/daily-ad-spend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/daily-ad-spend` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/expenses/meta-ads?page=${page}&limit=${limit} (frontend/src/services/api.ts:615)
`frontend/src/services/api.ts:615` calls `GET /api/admin/expenses/meta-ads?page=${page}&limit=${limit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/meta-ads` If this points at an external …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/expenses/sources (frontend/src/services/api.ts:586)
`frontend/src/services/api.ts:586` calls `GET /api/admin/expenses/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/sources` 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/admin/fixed-monthly-expenses${qs} (frontend/src/services/api.ts:880)
`frontend/src/services/api.ts:880` calls `GET /api/admin/fixed-monthly-expenses${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/fixed-monthly-expenses/<p>` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/shopify/orders/${encodeURIComponent(orderNumber)} (frontend/src/services/api.ts:336)
`frontend/src/services/api.ts:336` calls `GET /api/admin/magic-links/shopify/orders/${encodeURIComponent(orderNumber)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/orders/<p>` I…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/shopify/orders?limit=${limit}${allParam}${dateParam}${monthParam} (frontend/src/services/api.ts:328)
`frontend/src/services/api.ts:328` calls `GET /api/admin/magic-links/shopify/orders?limit=${limit}${allParam}${dateParam}${monthParam}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/shopify/products (frontend/src/services/api.ts:552)
`frontend/src/services/api.ts:552` calls `GET /api/admin/magic-links/shopify/products` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/products` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/shopify/products/${productId} (frontend/src/services/api.ts:556)
`frontend/src/services/api.ts:556` calls `GET /api/admin/magic-links/shopify/products/${productId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/products/<p>` If this points at a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/tickets (frontend/src/services/api.ts:1012)
`frontend/src/services/api.ts:1012` calls `GET /api/admin/magic-links/tickets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/tickets` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/tickets/${awb} (frontend/src/services/api.ts:1030)
`frontend/src/services/api.ts:1030` calls `GET /api/admin/magic-links/tickets/${awb}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/tickets/<p>` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links/tracking/${awb} (frontend/src/services/api.ts:1008)
`frontend/src/services/api.ts:1008` calls `GET /api/admin/magic-links/tracking/${awb}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/tracking/<p>` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/magic-links?page=${page}&limit=${limit} (frontend/src/services/api.ts:256)
`frontend/src/services/api.ts:256` calls `GET /api/admin/magic-links?page=${page}&limit=${limit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/pincodes/blocked (frontend/src/services/api.ts:991)
`frontend/src/services/api.ts:991` calls `GET /api/admin/pincodes/blocked` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/blocked` 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/admin/pincodes/cod-added-cities (frontend/src/services/api.ts:1330)
`frontend/src/services/api.ts:1330` calls `GET /api/admin/pincodes/cod-added-cities` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/cod-added-cities` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-analysis-dates (frontend/src/services/api.ts:1119)
`frontend/src/services/api.ts:1119` calls `GET /api/admin/sales/ads-analysis-dates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-analysis-dates` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-analysis-latest (frontend/src/services/api.ts:1115)
`frontend/src/services/api.ts:1115` calls `GET /api/admin/sales/ads-analysis-latest` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-analysis-latest` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-analysis/${date} (frontend/src/services/api.ts:1111)
`frontend/src/services/api.ts:1111` calls `GET /api/admin/sales/ads-analysis/${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-analysis/<p>` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-performance-all (frontend/src/services/api.ts:1127)
`frontend/src/services/api.ts:1127` calls `GET /api/admin/sales/ads-performance-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance-all` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-performance/${date} (frontend/src/services/api.ts:1123)
`frontend/src/services/api.ts:1123` calls `GET /api/admin/sales/ads-performance/${date}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance/<p>` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-performance/daily (frontend/src/services/api.ts:1107)
`frontend/src/services/api.ts:1107` calls `GET /api/admin/sales/ads-performance/daily` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance/daily` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ads-performance/status (frontend/src/services/api.ts:1095)
`frontend/src/services/api.ts:1095` calls `GET /api/admin/sales/ads-performance/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance/status` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/ai-prediction-data?startDate=${startDate} (frontend/src/services/api.ts:1408)
`frontend/src/services/api.ts:1408` calls `GET /api/admin/sales/ai-prediction-data?startDate=${startDate}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ai-prediction-data` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/backlog-orders (frontend/src/services/api.ts:332)
`frontend/src/services/api.ts:332` calls `GET /api/admin/sales/backlog-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/backlog-orders` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/breakeven-metrics (frontend/src/services/api.ts:1425)
`frontend/src/services/api.ts:1425` calls `GET /api/admin/sales/breakeven-metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/breakeven-metrics` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/daily-averages?days=${days} (frontend/src/services/api.ts:1315)
`frontend/src/services/api.ts:1315` calls `GET /api/admin/sales/daily-averages?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/daily-averages` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/failed-orders-analysis (frontend/src/services/api.ts:1326)
`frontend/src/services/api.ts:1326` calls `GET /api/admin/sales/failed-orders-analysis` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/failed-orders-analysis` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/prediction/${monthYear} (frontend/src/services/api.ts:1059)
`frontend/src/services/api.ts:1059` calls `GET /api/admin/sales/prediction/${monthYear}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/prediction/<p>` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/search-orders?query=${encodeURIComponent(query)} (frontend/src/services/api.ts:1055)
`frontend/src/services/api.ts:1055` calls `GET /api/admin/sales/search-orders?query=${encodeURIComponent(query)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/search-orders` If this points at …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/sales/variant-performance?days=${days} (frontend/src/services/api.ts:1362)
`frontend/src/services/api.ts:1362` calls `GET /api/admin/sales/variant-performance?days=${days}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/variant-performance` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/upload/${token} (frontend/src/services/api.ts:734)
`frontend/src/services/api.ts:734` calls `GET /api/upload/${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/upload/<p>` 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/upload/${token}/images (frontend/src/services/api.ts:750)
`frontend/src/services/api.ts:750` calls `GET /api/upload/${token}/images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/upload/<p>/images` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/bank-account/categories/${encodeURIComponent(name)}/tags (frontend/src/services/api.ts:927)
`frontend/src/services/api.ts:927` calls `PATCH /api/admin/bank-account/categories/${encodeURIComponent(name)}/tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/categories/<p>/tags` If…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/bank-account/categories/${encodeURIComponent(oldName)} (frontend/src/services/api.ts:914)
`frontend/src/services/api.ts:914` calls `PATCH /api/admin/bank-account/categories/${encodeURIComponent(oldName)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/categories/<p>` If this p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/bank-account/transactions/${id} (frontend/src/services/api.ts:958)
`frontend/src/services/api.ts:958` calls `PATCH /api/admin/bank-account/transactions/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/transactions/<p>` If this points at an external …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/bank-account/transactions/bulk/tags (frontend/src/services/api.ts:951)
`frontend/src/services/api.ts:951` calls `PATCH /api/admin/bank-account/transactions/bulk/tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/transactions/bulk/tags` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/admin/magic-links/tickets/${id} (frontend/src/services/api.ts:1023)
`frontend/src/services/api.ts:1023` calls `PATCH /api/admin/magic-links/tickets/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/tickets/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/abandoned-checkouts (frontend/src/services/api.ts:1157)
`frontend/src/services/api.ts:1157` calls `POST /api/admin/abandoned-checkouts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/abandoned-checkouts` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/abandoned-checkouts/template (frontend/src/services/api.ts:1147)
`frontend/src/services/api.ts:1147` calls `POST /api/admin/abandoned-checkouts/template` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/abandoned-checkouts/template` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/attendance/advances (frontend/src/services/api.ts:1213)
`frontend/src/services/api.ts:1213` calls `POST /api/admin/attendance/advances` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/advances` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/attendance/employees (frontend/src/services/api.ts:1184)
`frontend/src/services/api.ts:1184` calls `POST /api/admin/attendance/employees` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/employees` 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/admin/attendance/hourly-logs (frontend/src/services/api.ts:1227)
`frontend/src/services/api.ts:1227` calls `POST /api/admin/attendance/hourly-logs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/hourly-logs` 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/admin/attendance/payments (frontend/src/services/api.ts:1220)
`frontend/src/services/api.ts:1220` calls `POST /api/admin/attendance/payments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/payments` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/attendance/records (frontend/src/services/api.ts:1206)
`frontend/src/services/api.ts:1206` calls `POST /api/admin/attendance/records` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/records` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/auth/login (frontend/src/services/api.ts:221)
`frontend/src/services/api.ts:221` calls `POST /api/admin/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/auth/login` 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/admin/auth/register (frontend/src/services/api.ts:234)
`frontend/src/services/api.ts:234` calls `POST /api/admin/auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/auth/register` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/bank-account/categories (frontend/src/services/api.ts:907)
`frontend/src/services/api.ts:907` calls `POST /api/admin/bank-account/categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/categories` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/bank-account/narration-rules (frontend/src/services/api.ts:969)
`frontend/src/services/api.ts:969` calls `POST /api/admin/bank-account/narration-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/narration-rules` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/bank-account/transactions/bulk (frontend/src/services/api.ts:938)
`frontend/src/services/api.ts:938` calls `POST /api/admin/bank-account/transactions/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/bank-account/transactions/bulk` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/expenses/daily-ad-spend (frontend/src/services/api.ts:680)
`frontend/src/services/api.ts:680` calls `POST /api/admin/expenses/daily-ad-spend` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/daily-ad-spend` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/expenses/meta-ads (frontend/src/services/api.ts:638)
`frontend/src/services/api.ts:638` calls `POST /api/admin/expenses/meta-ads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/meta-ads` 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/admin/expenses/sources (frontend/src/services/api.ts:594)
`frontend/src/services/api.ts:594` calls `POST /api/admin/expenses/sources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/expenses/sources` 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/admin/fixed-monthly-expenses (frontend/src/services/api.ts:884)
`frontend/src/services/api.ts:884` calls `POST /api/admin/fixed-monthly-expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/fixed-monthly-expenses` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links (frontend/src/services/api.ts:266)
`frontend/src/services/api.ts:266` calls `POST /api/admin/magic-links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links` 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/admin/magic-links/generate-complaint (frontend/src/services/api.ts:1034)
`frontend/src/services/api.ts:1034` calls `POST /api/admin/magic-links/generate-complaint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/generate-complaint` If this points at an external …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shiprocket/clear-cache (frontend/src/services/api.ts:360)
`frontend/src/services/api.ts:360` calls `POST /api/admin/magic-links/shiprocket/clear-cache` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shiprocket/clear-cache` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shiprocket/fetch-shipping-charge (frontend/src/services/api.ts:350)
`frontend/src/services/api.ts:350` calls `POST /api/admin/magic-links/shiprocket/fetch-shipping-charge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shiprocket/fetch-shipping-charge` If …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shiprocket/sync-shipping-charges (frontend/src/services/api.ts:369)
`frontend/src/services/api.ts:369` calls `POST /api/admin/magic-links/shiprocket/sync-shipping-charges` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shiprocket/sync-shipping-charges` If …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shopify/customers/${customerId}/tags (frontend/src/services/api.ts:404)
`frontend/src/services/api.ts:404` calls `POST /api/admin/magic-links/shopify/customers/${customerId}/tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/customers/<p>/tags` If th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shopify/customers/bulk-tags (frontend/src/services/api.ts:393)
`frontend/src/services/api.ts:393` calls `POST /api/admin/magic-links/shopify/customers/bulk-tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/customers/bulk-tags` If this point…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shopify/orders/clear-cache (frontend/src/services/api.ts:340)
`frontend/src/services/api.ts:340` calls `POST /api/admin/magic-links/shopify/orders/clear-cache` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/orders/clear-cache` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/shopify/update-delivery-status (frontend/src/services/api.ts:379)
`frontend/src/services/api.ts:379` calls `POST /api/admin/magic-links/shopify/update-delivery-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/update-delivery-status` If this…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/magic-links/tickets (frontend/src/services/api.ts:1016)
`frontend/src/services/api.ts:1016` calls `POST /api/admin/magic-links/tickets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/tickets` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/pincodes/blocked (frontend/src/services/api.ts:995)
`frontend/src/services/api.ts:995` calls `POST /api/admin/pincodes/blocked` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/blocked` 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/admin/pincodes/cod-added-cities (frontend/src/services/api.ts:1334)
`frontend/src/services/api.ts:1334` calls `POST /api/admin/pincodes/cod-added-cities` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/pincodes/cod-added-cities` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/acknowledge-orders (frontend/src/services/api.ts:431)
`frontend/src/services/api.ts:431` calls `POST /api/admin/sales/acknowledge-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/acknowledge-orders` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/ads-chat (frontend/src/services/api.ts:1131)
`frontend/src/services/api.ts:1131` calls `POST /api/admin/sales/ads-chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-chat` 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/admin/sales/ads-performance (frontend/src/services/api.ts:1088)
`frontend/src/services/api.ts:1088` calls `POST /api/admin/sales/ads-performance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ads-performance` 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/admin/sales/analyze-ads (frontend/src/services/api.ts:1081)
`frontend/src/services/api.ts:1081` calls `POST /api/admin/sales/analyze-ads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/analyze-ads` 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/admin/sales/daily-order-stats/backfill (frontend/src/services/api.ts:1281)
`frontend/src/services/api.ts:1281` calls `POST /api/admin/sales/daily-order-stats/backfill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/daily-order-stats/backfill` If this points at an exter…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/daily-pnl/backfill (frontend/src/services/api.ts:1387)
`frontend/src/services/api.ts:1387` calls `POST /api/admin/sales/daily-pnl/backfill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/daily-pnl/backfill` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/daily-roas/backfill (frontend/src/services/api.ts:705)
`frontend/src/services/api.ts:705` calls `POST /api/admin/sales/daily-roas/backfill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/daily-roas/backfill` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/daily-shipping/backfill (frontend/src/services/api.ts:729)
`frontend/src/services/api.ts:729` calls `POST /api/admin/sales/daily-shipping/backfill` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/daily-shipping/backfill` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/discard-orders (frontend/src/services/api.ts:485)
`frontend/src/services/api.ts:485` calls `POST /api/admin/sales/discard-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/discard-orders` 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/admin/sales/generate-incomplete-address-message (frontend/src/services/api.ts:1041)
`frontend/src/services/api.ts:1041` calls `POST /api/admin/sales/generate-incomplete-address-message` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/generate-incomplete-address-message` If this …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/generate-multiple-orders-message (frontend/src/services/api.ts:1048)
`frontend/src/services/api.ts:1048` calls `POST /api/admin/sales/generate-multiple-orders-message` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/generate-multiple-orders-message` If this points…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/mark-rto (frontend/src/services/api.ts:512)
`frontend/src/services/api.ts:512` calls `POST /api/admin/sales/mark-rto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/mark-rto` 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/admin/sales/predict (frontend/src/services/api.ts:1063)
`frontend/src/services/api.ts:1063` calls `POST /api/admin/sales/predict` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/predict` 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/admin/sales/predict-stock (frontend/src/services/api.ts:1074)
`frontend/src/services/api.ts:1074` calls `POST /api/admin/sales/predict-stock` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/predict-stock` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/sales/ticket-raised-orders (frontend/src/services/api.ts:458)
`frontend/src/services/api.ts:458` calls `POST /api/admin/sales/ticket-raised-orders` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/sales/ticket-raised-orders` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3001/api/admin/auth/login (test-api.js:3)
`test-api.js:3` calls `POST http://localhost:3001/api/admin/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3001/api/admin/auth/login` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/abandoned-checkouts/${id}/status (frontend/src/services/api.ts:1167)
`frontend/src/services/api.ts:1167` calls `PUT /api/admin/abandoned-checkouts/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/abandoned-checkouts/<p>/status` If this points at an external…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/attendance/employees/${id} (frontend/src/services/api.ts:1191)
`frontend/src/services/api.ts:1191` calls `PUT /api/admin/attendance/employees/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/attendance/employees/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/fixed-monthly-expenses/${id} (frontend/src/services/api.ts:891)
`frontend/src/services/api.ts:891` calls `PUT /api/admin/fixed-monthly-expenses/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/fixed-monthly-expenses/<p>` If this points at an external API, pre…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/magic-links/shopify/products/bulk-update-prices (frontend/src/services/api.ts:574)
`frontend/src/services/api.ts:574` calls `PUT /api/admin/magic-links/shopify/products/bulk-update-prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/magic-links/shopify/products/bulk-update-prices…
Dangling fetchHelper:request
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/analysis/StuckOrdersAnalysis.tsx:122
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/src/services/shiprocketService.ts:143
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/src/services/shopifyService.ts:43
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/services/api.ts:211
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — test-api.js:3
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 Frontend route `/monthly` has no Link/navigate to it — frontend/src/pages/GSTReportsPage.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 10 occurrences Frontend route `dashboard` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
10 occurrences
repo-level (10 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 5 occurrences Frontend route `failed-orders` has no Link/navigate to it — frontend/src/pages/AnalysisPage.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
5 occurrences
repo-level (5 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 4 occurrences Frontend route `meta-ads` has no Link/navigate to it — frontend/src/pages/ExpensesPage.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 5 occurrences Frontend route `products` has no Link/navigate to it — frontend/src/pages/ToolsPage.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
5 occurrences
repo-level (5 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/pages/analysis/StuckOrdersAnalysis.tsx:122
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/pages/analysis/StuckOrdersAnalysis.tsx:122 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/src/services/api.ts:188
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/src/services/api.ts:188 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 46 placeholder/mock markers across 15 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 256 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/pages/BankAccountPage.tsx:918
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
12 tests / 118 src (ratio 0.10).
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `fixViaAWB_v2` in backend/scripts/fixViaAWB.ts:125
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `hasOld` in backend/src/routes/cogs.ts:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/check_db_history.js:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/backfill-order-stats.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/backfill-pnl.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/backfill-roas.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/backfill-shipping.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/debugPB1118S.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/debugSync.ts:27
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/deepSyncWallet.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/exploreShiprocket.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/fixOldFailedOrders.ts:29
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/fixViaAWB.ts:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/historicalSync.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/listMissingOrders.ts:30
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/listSync153.ts:20
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/listTerminalSync.ts:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/migrate-pincodes-full.ts:10
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testAWBEndpoint.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testAwbSearch.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testCloneFetch.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testShipmentId.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testShiprocketDates.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testShiprocketFetch.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testShiprocketHistory.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/testShiprocketQuery.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/index.ts:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/routes/magicLinks.ts:870
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/routes/sales.ts:705
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/services/aiService.ts:88
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/services/shiprocketService.ts:171
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/services/shopifyService.ts:205
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/test_shiprocket_delivery.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/pages/analysis/AdsAnalysis.tsx:230
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/pages/BankAccountPage.tsx:254
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/pages/GSTMonthlyReports.tsx:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-api.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — test-local.js:4
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /blocked/:pinCode
`backend/src/routes/pincodes.ts` declares `DELETE /blocked/:pinCode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /cod-added-cities/:city
`backend/src/routes/pincodes.ts` declares `DELETE /cod-added-cities/:city` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /configuration/:id
`backend/src/routes/cogs.ts` declares `DELETE /configuration/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /hourly-logs/:employeeId/:dateStr
`backend/src/routes/attendance.ts` declares `DELETE /hourly-logs/:employeeId/:dateStr` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /narration-rules/:id
`backend/src/routes/bankAccount.ts` declares `DELETE /narration-rules/: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 /
`backend/src/routes/abandonedCheckouts.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 /api/health
`backend/src/index.ts` declares `GET /api/health` 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 /blocked
`backend/src/routes/pincodes.ts` declares `GET /blocked` 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 /categories
`backend/src/routes/bankAccount.ts` declares `GET /categories` 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 /cod-added-cities
`backend/src/routes/pincodes.ts` declares `GET /cod-added-cities` 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 /configuration
`backend/src/routes/cogs.ts` declares `GET /configuration` 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 /configuration/versions
`backend/src/routes/cogs.ts` declares `GET /configuration/versions` 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 /employees
`backend/src/routes/attendance.ts` declares `GET /employees` 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 /employees/stats
`backend/src/routes/attendance.ts` declares `GET /employees/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /hourly-logs/all
`backend/src/routes/attendance.ts` declares `GET /hourly-logs/all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /hourly-logs/month/:month
`backend/src/routes/attendance.ts` declares `GET /hourly-logs/month/:month` 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 /narration-rules
`backend/src/routes/bankAccount.ts` declares `GET /narration-rules` 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 /records
`backend/src/routes/attendance.ts` declares `GET /records` 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 /records/month/:month
`backend/src/routes/attendance.ts` declares `GET /records/month/:month` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stats
`backend/src/routes/deliveryDates.ts` declares `GET /stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /template
`backend/src/routes/abandonedCheckouts.ts` declares `GET /template` 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 /transactions
`backend/src/routes/bankAccount.ts` declares `GET /transactions` 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/abandonedCheckouts.ts` 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 /advances
`backend/src/routes/attendance.ts` declares `POST /advances` 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 /blocked
`backend/src/routes/pincodes.ts` declares `POST /blocked` 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 /categories
`backend/src/routes/bankAccount.ts` declares `POST /categories` 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 /cod-added-cities
`backend/src/routes/pincodes.ts` declares `POST /cod-added-cities` 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 /configuration
`backend/src/routes/cogs.ts` declares `POST /configuration` 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 /employees
`backend/src/routes/attendance.ts` declares `POST /employees` 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 /hourly-logs
`backend/src/routes/attendance.ts` declares `POST /hourly-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: POST /narration-rules
`backend/src/routes/bankAccount.ts` declares `POST /narration-rules` 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 /payments
`backend/src/routes/attendance.ts` declares `POST /payments` 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 /records
`backend/src/routes/attendance.ts` declares `POST /records` 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 /template
`backend/src/routes/abandonedCheckouts.ts` declares `POST /template` 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/routes/deliveryDates.ts` 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: PUT /:id/status
`backend/src/routes/abandonedCheckouts.ts` declares `PUT /: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: PUT /configuration/:id
`backend/src/routes/cogs.ts` declares `PUT /configuration/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /employees/:id
`backend/src/routes/attendance.ts` declares `PUT /employees/: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: USE /api/admin/abandoned-checkouts
`backend/src/index.ts` declares `USE /api/admin/abandoned-checkouts` 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/attendance
`backend/src/index.ts` declares `USE /api/admin/attendance` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/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/bank-account
`backend/src/index.ts` declares `USE /api/admin/bank-account` 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/cogs
`backend/src/index.ts` declares `USE /api/admin/cogs` 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/delivery-dates
`backend/src/index.ts` declares `USE /api/admin/delivery-dates` 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/expenses
`backend/src/index.ts` declares `USE /api/admin/expenses` 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/fixed-monthly-expenses
`backend/src/index.ts` declares `USE /api/admin/fixed-monthly-expenses` 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/magic-links
`backend/src/index.ts` declares `USE /api/admin/magic-links` 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/pincodes
`backend/src/index.ts` declares `USE /api/admin/pincodes` 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/sales
`backend/src/index.ts` declares `USE /api/admin/sales` 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/upload
`backend/src/index.ts` declares `USE /api/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 quality Complexity conf 1.00 Very large file: backend/src/routes/sales.ts (1834 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/BankAccountPage.tsx (1211 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/DashboardPage.tsx (1859 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/SalesPage.tsx (2829 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/9236c075-9406-4f2d-8606-5a8e31419f00/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9236c075-9406-4f2d-8606-5a8e31419f00/

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.