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

sovest905-blip/cosplayhub

https://github.com/sovest905-blip/cosplayhub · scanned 2026-06-16 00:18 UTC (2 months, 2 weeks ago)

247 raw signals (0 security + 247 graph)

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

Complete repo analysis

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

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

Showing 162 of 235 actionable findings. 247 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/v1/auth/${kind}/ (web/app/cabinet/page.tsx:551)
`web/app/cabinet/page.tsx:551` calls `DELETE /api/v1/auth/${kind}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/favorites/${kind}/${objectId}/ (web/app/cabinet/page.tsx:754)
`web/app/cabinet/page.tsx:754` calls `DELETE /api/v1/favorites/${kind}/${objectId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/favorites/<p>/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/follow/${userId}/ (web/app/cabinet/page.tsx:749)
`web/app/cabinet/page.tsx:749` calls `DELETE /api/v1/follow/${userId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/listings/${id}/ (web/app/cabinet/page.tsx:560)
`web/app/cabinet/page.tsx:560` calls `DELETE /api/v1/listings/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/listings/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/looks/${id}/ (web/app/cabinet/page.tsx:616)
`web/app/cabinet/page.tsx:616` calls `DELETE /api/v1/looks/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/looks/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/products/${id}/ (web/app/cabinet/page.tsx:644)
`web/app/cabinet/page.tsx:644` calls `DELETE /api/v1/products/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/products/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/profiles/me/photos/${id}/ (web/app/cabinet/page.tsx:592)
`web/app/cabinet/page.tsx:592` calls `DELETE /api/v1/profiles/me/photos/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/profiles/me/photos/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/slots/${id}/ (web/app/cabinet/page.tsx:673)
`web/app/cabinet/page.tsx:673` calls `DELETE /api/v1/slots/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/slots/${slot.id}/book/ (web/app/components/SlotList.tsx:64)
`web/app/components/SlotList.tsx:64` calls `DELETE /api/v1/slots/${slot.id}/book/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots/<p>/book` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/workshops/${id}/ (web/app/cabinet/page.tsx:726)
`web/app/cabinet/page.tsx:726` calls `DELETE /api/v1/workshops/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/v1/workshops/${wsId}/photos/${photoId}/ (web/app/cabinet/page.tsx:742)
`web/app/cabinet/page.tsx:742` calls `DELETE /api/v1/workshops/${wsId}/photos/${photoId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops/<p>/photos/<p>` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1${path} (web/app/admin-panel/page.tsx:53)
`web/app/admin-panel/page.tsx:53` calls `GET /api/v1${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1${path} (web/app/teams/[id]/page.tsx:9)
`web/app/teams/[id]/page.tsx:9` calls `GET /api/v1${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/analytics/me/ (web/app/cabinet/page.tsx:244)
`web/app/cabinet/page.tsx:244` calls `GET /api/v1/analytics/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/analytics/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/cabinet/page.tsx:203)
`web/app/cabinet/page.tsx:203` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/cabinet/page.tsx:344)
`web/app/cabinet/page.tsx:344` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/AuthNav.tsx:16)
`web/app/components/AuthNav.tsx:16` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/FollowButton.tsx:26)
`web/app/components/FollowButton.tsx:26` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/FollowButton.tsx:49)
`web/app/components/FollowButton.tsx:49` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/GatedButton.tsx:23)
`web/app/components/GatedButton.tsx:23` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/GoingButton.tsx:25)
`web/app/components/GoingButton.tsx:25` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/JobListings.tsx:18)
`web/app/components/JobListings.tsx:18` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/LikeButton.tsx:19)
`web/app/components/LikeButton.tsx:19` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/MarketListings.tsx:19)
`web/app/components/MarketListings.tsx:19` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/MessageButton.tsx:23)
`web/app/components/MessageButton.tsx:23` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/MessagesPanel.tsx:52)
`web/app/components/MessagesPanel.tsx:52` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/MobileMenu.tsx:49)
`web/app/components/MobileMenu.tsx:49` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/OrderButton.tsx:26)
`web/app/components/OrderButton.tsx:26` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/OwnerOnly.tsx:21)
`web/app/components/OwnerOnly.tsx:21` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/PostListingButton.tsx:23)
`web/app/components/PostListingButton.tsx:23` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/ProCta.tsx:28)
`web/app/components/ProCta.tsx:28` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/SaveButton.tsx:45)
`web/app/components/SaveButton.tsx:45` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/SlotList.tsx:38)
`web/app/components/SlotList.tsx:38` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/components/SlotList.tsx:47)
`web/app/components/SlotList.tsx:47` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/guides/new/page.tsx:15)
`web/app/guides/new/page.tsx:15` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/notifications/page.tsx:33)
`web/app/notifications/page.tsx:33` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me/ (web/app/teams/new/page.tsx:15)
`web/app/teams/new/page.tsx:15` calls `GET /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/billing/me/ (web/app/cabinet/page.tsx:319)
`web/app/cabinet/page.tsx:319` calls `GET /api/v1/billing/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/billing/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/billing/me/ (web/app/cabinet/page.tsx:343)
`web/app/cabinet/page.tsx:343` calls `GET /api/v1/billing/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/billing/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/conversations/ (web/app/cabinet/page.tsx:192)
`web/app/cabinet/page.tsx:192` calls `GET /api/v1/conversations/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/conversations` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/conversations/ (web/app/components/MessagesPanel.tsx:59)
`web/app/components/MessagesPanel.tsx:59` calls `GET /api/v1/conversations/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/conversations` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/conversations/${activeId}/messages/ (web/app/components/MessagesPanel.tsx:100)
`web/app/components/MessagesPanel.tsx:100` calls `GET /api/v1/conversations/${activeId}/messages/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/conversations/<p>/messages` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/events/${eventId}/attend/ (web/app/components/GoingButton.tsx:27)
`web/app/components/GoingButton.tsx:27` calls `GET /api/v1/events/${eventId}/attend/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/events/<p>/attend` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/events/mine/ (web/app/cabinet/page.tsx:240)
`web/app/cabinet/page.tsx:240` calls `GET /api/v1/events/mine/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/events/mine` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/favorites/ (web/app/cabinet/page.tsx:271)
`web/app/cabinet/page.tsx:271` calls `GET /api/v1/favorites/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/favorites` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/favorites/${kind}/${objectId}/ (web/app/components/SaveButton.tsx:27)
`web/app/components/SaveButton.tsx:27` calls `GET /api/v1/favorites/${kind}/${objectId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/favorites/<p>/<p>` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/favorites/${kind}/${objectId}/ (web/app/components/SaveButton.tsx:50)
`web/app/components/SaveButton.tsx:50` calls `GET /api/v1/favorites/${kind}/${objectId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/favorites/<p>/<p>` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/feed/ (web/app/feed/page.tsx:28)
`web/app/feed/page.tsx:28` calls `GET /api/v1/feed/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/feed` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/follow/${userId}/ (web/app/components/FollowButton.tsx:31)
`web/app/components/FollowButton.tsx:31` calls `GET /api/v1/follow/${userId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/follow/${userId}/ (web/app/components/FollowButton.tsx:54)
`web/app/components/FollowButton.tsx:54` calls `GET /api/v1/follow/${userId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/<p>` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/follow/followers/ (web/app/cabinet/page.tsx:267)
`web/app/cabinet/page.tsx:267` calls `GET /api/v1/follow/followers/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/followers` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/follow/following/ (web/app/cabinet/page.tsx:263)
`web/app/cabinet/page.tsx:263` calls `GET /api/v1/follow/following/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/following` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/listings/ (web/app/cabinet/page.tsx:255)
`web/app/cabinet/page.tsx:255` calls `GET /api/v1/listings/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/listings` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/listings/public/ (web/app/cabinet/page.tsx:568)
`web/app/cabinet/page.tsx:568` calls `GET /api/v1/listings/public/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/listings/public` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/looks/${lookId}/like/ (web/app/components/LikeButton.tsx:21)
`web/app/components/LikeButton.tsx:21` calls `GET /api/v1/looks/${lookId}/like/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/looks/<p>/like` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/looks/?mine=1 (web/app/cabinet/page.tsx:279)
`web/app/cabinet/page.tsx:279` calls `GET /api/v1/looks/?mine=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/looks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/messages/unread-count/ (web/app/components/AuthNav.tsx:31)
`web/app/components/AuthNav.tsx:31` calls `GET /api/v1/messages/unread-count/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/messages/unread-count` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/messages/unread-count/ (web/app/components/MobileMenu.tsx:55)
`web/app/components/MobileMenu.tsx:55` calls `GET /api/v1/messages/unread-count/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/messages/unread-count` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/notifications/ (web/app/notifications/page.tsx:40)
`web/app/notifications/page.tsx:40` calls `GET /api/v1/notifications/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/notifications` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/notifications/unread-count/ (web/app/components/AuthNav.tsx:32)
`web/app/components/AuthNav.tsx:32` calls `GET /api/v1/notifications/unread-count/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/notifications/unread-count` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/notifications/unread-count/ (web/app/components/MobileMenu.tsx:57)
`web/app/components/MobileMenu.tsx:57` calls `GET /api/v1/notifications/unread-count/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/notifications/unread-count` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/orders/ (web/app/cabinet/page.tsx:232)
`web/app/cabinet/page.tsx:232` calls `GET /api/v1/orders/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/orders` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/orders/incoming/ (web/app/cabinet/page.tsx:248)
`web/app/cabinet/page.tsx:248` calls `GET /api/v1/orders/incoming/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/orders/incoming` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/products/?mine=1 (web/app/cabinet/page.tsx:287)
`web/app/cabinet/page.tsx:287` calls `GET /api/v1/products/?mine=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/products` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/profiles/fan-matches/ (web/app/cabinet/page.tsx:761)
`web/app/cabinet/page.tsx:761` calls `GET /api/v1/profiles/fan-matches/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/profiles/fan-matches` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/profiles/me/photos/ (web/app/cabinet/page.tsx:275)
`web/app/cabinet/page.tsx:275` calls `GET /api/v1/profiles/me/photos/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/profiles/me/photos` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/search/?q=${encodeURIComponent(term)} (web/app/components/SearchBox.tsx:50)
`web/app/components/SearchBox.tsx:50` calls `GET /api/v1/search/?q=${encodeURIComponent(term)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/search` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/slots/?mine=1 (web/app/cabinet/page.tsx:295)
`web/app/cabinet/page.tsx:295` calls `GET /api/v1/slots/?mine=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/slots/?owner=${ownerId} (web/app/components/SlotList.tsx:33)
`web/app/components/SlotList.tsx:33` calls `GET /api/v1/slots/?owner=${ownerId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/teams/?mine=1 (web/app/cabinet/page.tsx:303)
`web/app/cabinet/page.tsx:303` calls `GET /api/v1/teams/?mine=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/teams` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/workshops/mine/ (web/app/cabinet/page.tsx:311)
`web/app/cabinet/page.tsx:311` calls `GET /api/v1/workshops/mine/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops/mine` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/workshops/mine/ (web/app/cabinet/page.tsx:349)
`web/app/cabinet/page.tsx:349` calls `GET /api/v1/workshops/mine/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops/mine` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/auth/me/ (web/app/cabinet/page.tsx:376)
`web/app/cabinet/page.tsx:376` calls `PATCH /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/auth/me/ (web/app/cabinet/page.tsx:393)
`web/app/cabinet/page.tsx:393` calls `PATCH /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/auth/me/ (web/app/cabinet/page.tsx:409)
`web/app/cabinet/page.tsx:409` calls `PATCH /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/auth/me/ (web/app/cabinet/page.tsx:426)
`web/app/cabinet/page.tsx:426` calls `PATCH /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/auth/me/ (web/app/cabinet/page.tsx:438)
`web/app/cabinet/page.tsx:438` calls `PATCH /api/v1/auth/me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/listings/${id}/ (web/app/cabinet/page.tsx:520)
`web/app/cabinet/page.tsx:520` calls `PATCH /api/v1/listings/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/listings/<p>` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/v1/orders/incoming/${orderId}/ (web/app/cabinet/page.tsx:460)
`web/app/cabinet/page.tsx:460` calls `PATCH /api/v1/orders/incoming/${orderId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/orders/incoming/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/${kind}/ (web/app/cabinet/page.tsx:535)
`web/app/cabinet/page.tsx:535` calls `POST /api/v1/auth/${kind}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/change-email/ (web/app/cabinet/page.tsx:793)
`web/app/cabinet/page.tsx:793` calls `POST /api/v1/auth/change-email/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/change-email` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/change-email/confirm/ (web/app/cabinet/page.tsx:807)
`web/app/cabinet/page.tsx:807` calls `POST /api/v1/auth/change-email/confirm/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/change-email/confirm` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/change-password/ (web/app/cabinet/page.tsx:778)
`web/app/cabinet/page.tsx:778` calls `POST /api/v1/auth/change-password/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/change-password` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/delete-account/ (web/app/cabinet/page.tsx:823)
`web/app/cabinet/page.tsx:823` calls `POST /api/v1/auth/delete-account/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/delete-account` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/forgot-password/ (web/app/auth/forgot-password/page.tsx:28)
`web/app/auth/forgot-password/page.tsx:28` calls `POST /api/v1/auth/forgot-password/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/forgot-password` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/login/ (web/app/auth/login/page.tsx:29)
`web/app/auth/login/page.tsx:29` calls `POST /api/v1/auth/login/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout/ (web/app/cabinet/page.tsx:2320)
`web/app/cabinet/page.tsx:2320` calls `POST /api/v1/auth/logout/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout/ (web/app/components/AuthNav.tsx:44)
`web/app/components/AuthNav.tsx:44` calls `POST /api/v1/auth/logout/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout/ (web/app/components/MobileMenu.tsx:81)
`web/app/components/MobileMenu.tsx:81` calls `POST /api/v1/auth/logout/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/reset-password/ (web/app/auth/forgot-password/page.tsx:82)
`web/app/auth/forgot-password/page.tsx:82` calls `POST /api/v1/auth/reset-password/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/reset-password` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/send-otp/ (web/app/auth/verify-email/page.tsx:74)
`web/app/auth/verify-email/page.tsx:74` calls `POST /api/v1/auth/send-otp/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/send-otp` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/verify-otp/ (web/app/auth/verify-email/page.tsx:50)
`web/app/auth/verify-email/page.tsx:50` calls `POST /api/v1/auth/verify-otp/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/verify-otp` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/verify-telegram-otp/ (web/app/auth/verify-phone/page.tsx:20)
`web/app/auth/verify-phone/page.tsx:20` calls `POST /api/v1/auth/verify-telegram-otp/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/verify-telegram-otp` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/billing/activate/ (web/app/cabinet/page.tsx:337)
`web/app/cabinet/page.tsx:337` calls `POST /api/v1/billing/activate/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/billing/activate` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/billing/activate/ (web/app/components/ProCta.tsx:38)
`web/app/components/ProCta.tsx:38` calls `POST /api/v1/billing/activate/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/billing/activate` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/bookings/${bookingId}/ (web/app/cabinet/page.tsx:679)
`web/app/cabinet/page.tsx:679` calls `POST /api/v1/bookings/${bookingId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/bookings/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/conversations/ (web/app/components/MessagesPanel.tsx:73)
`web/app/components/MessagesPanel.tsx:73` calls `POST /api/v1/conversations/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/conversations` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/conversations/${activeId}/messages/ (web/app/components/MessagesPanel.tsx:121)
`web/app/components/MessagesPanel.tsx:121` calls `POST /api/v1/conversations/${activeId}/messages/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/conversations/<p>/messages` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/follow/${userId}/ (web/app/cabinet/page.tsx:768)
`web/app/cabinet/page.tsx:768` calls `POST /api/v1/follow/${userId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/follow/<p>` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/guides/ (web/app/guides/new/page.tsx:28)
`web/app/guides/new/page.tsx:28` calls `POST /api/v1/guides/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/guides` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/guides/${data.id}/photos/ (web/app/guides/new/page.tsx:35)
`web/app/guides/new/page.tsx:35` calls `POST /api/v1/guides/${data.id}/photos/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/guides/<p>/photos` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/looks/ (web/app/cabinet/page.tsx:608)
`web/app/cabinet/page.tsx:608` calls `POST /api/v1/looks/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/looks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/notifications/mark-read/ (web/app/notifications/page.tsx:45)
`web/app/notifications/page.tsx:45` calls `POST /api/v1/notifications/mark-read/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/notifications/mark-read` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders/ (web/app/components/OrderButton.tsx:38)
`web/app/components/OrderButton.tsx:38` calls `POST /api/v1/orders/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/orders` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/orders/${orderId}/review/ (web/app/cabinet/page.tsx:447)
`web/app/cabinet/page.tsx:447` calls `POST /api/v1/orders/${orderId}/review/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/orders/<p>/review` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/products/ (web/app/cabinet/page.tsx:633)
`web/app/cabinet/page.tsx:633` calls `POST /api/v1/products/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/products` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/profiles/me/photos/ (web/app/cabinet/page.tsx:584)
`web/app/cabinet/page.tsx:584` calls `POST /api/v1/profiles/me/photos/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/profiles/me/photos` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/slots/ (web/app/cabinet/page.tsx:659)
`web/app/cabinet/page.tsx:659` calls `POST /api/v1/slots/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/slots/${slot.id}/book/ (web/app/components/SlotList.tsx:49)
`web/app/components/SlotList.tsx:49` calls `POST /api/v1/slots/${slot.id}/book/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/slots/<p>/book` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/teams/ (web/app/teams/new/page.tsx:30)
`web/app/teams/new/page.tsx:30` calls `POST /api/v1/teams/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/teams` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/workshops/ (web/app/cabinet/page.tsx:701)
`web/app/cabinet/page.tsx:701` calls `POST /api/v1/workshops/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/workshops/${wsId}/photos/ (web/app/cabinet/page.tsx:734)
`web/app/cabinet/page.tsx:734` calls `POST /api/v1/workshops/${wsId}/photos/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/workshops/<p>/photos` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`backend/config/urls.py` declares `ANY /` 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: ANY /admin-panel/invites/
`backend/config/urls.py` declares `ANY /admin-panel/invites/` 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: ANY /admin-panel/invites/<int:pk>/
`backend/config/urls.py` declares `ANY /admin-panel/invites/<int:pk>/` 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: ANY /admin-panel/listings/
`backend/config/urls.py` declares `ANY /admin-panel/listings/` 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: ANY /admin-panel/listings/<int:pk>/delete/
`backend/config/urls.py` declares `ANY /admin-panel/listings/<int:pk>/delete/` 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: ANY /admin-panel/listings/<int:pk>/set-active/
`backend/config/urls.py` declares `ANY /admin-panel/listings/<int:pk>/set-active/` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/listings/<int:pk>/update/
`backend/config/urls.py` declares `ANY /admin-panel/listings/<int:pk>/update/` 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: ANY /admin-panel/orders/
`backend/config/urls.py` declares `ANY /admin-panel/orders/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/orders/<int:pk>/set-status/
`backend/config/urls.py` declares `ANY /admin-panel/orders/<int:pk>/set-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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/products/
`backend/config/urls.py` declares `ANY /admin-panel/products/` 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: ANY /admin-panel/products/<int:pk>/delete/
`backend/config/urls.py` declares `ANY /admin-panel/products/<int:pk>/delete/` 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: ANY /admin-panel/products/<int:pk>/set-active/
`backend/config/urls.py` declares `ANY /admin-panel/products/<int:pk>/set-active/` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/products/<int:pk>/update/
`backend/config/urls.py` declares `ANY /admin-panel/products/<int:pk>/update/` 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: ANY /admin-panel/slots/<int:pk>/
`backend/config/urls.py` declares `ANY /admin-panel/slots/<int:pk>/` 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: ANY /admin-panel/stats/
`backend/config/urls.py` declares `ANY /admin-panel/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: ANY /admin-panel/subscriptions/
`backend/config/urls.py` declares `ANY /admin-panel/subscriptions/` 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: ANY /admin-panel/subscriptions/<int:pk>/
`backend/config/urls.py` declares `ANY /admin-panel/subscriptions/<int:pk>/` 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: ANY /admin-panel/users/
`backend/config/urls.py` declares `ANY /admin-panel/users/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/delete/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/delete/` 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: ANY /admin-panel/users/<int:pk>/photos/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/photos/` 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: ANY /admin-panel/users/<int:pk>/photos/<int:photo_id>/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/photos/<int:photo_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/products/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/products/` 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: ANY /admin-panel/users/<int:pk>/reset-password/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/reset-password/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/set-active/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/set-active/` 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: ANY /admin-panel/users/<int:pk>/set-roles/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/set-roles/` 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: ANY /admin-panel/users/<int:pk>/set-staff/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/set-staff/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/slots/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/slots/` 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: ANY /admin-panel/users/<int:pk>/subscriptions/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/subscriptions/` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/subscriptions/<int:target_id>/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/subscriptions/<int:target_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin-panel/users/<int:pk>/workshops/
`backend/config/urls.py` declares `ANY /admin-panel/users/<int:pk>/workshops/` 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: ANY /admin-panel/workshops/
`backend/config/urls.py` declares `ANY /admin-panel/workshops/` 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: ANY /admin-panel/workshops/<int:pk>/
`backend/config/urls.py` declares `ANY /admin-panel/workshops/<int:pk>/` 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: ANY /admin-panel/workshops/<int:pk>/delete/
`backend/config/urls.py` declares `ANY /admin-panel/workshops/<int:pk>/delete/` 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: ANY /admin/
`backend/config/urls.py` declares `ANY /admin/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /analytics/me/
`backend/config/urls.py` declares `ANY /analytics/me/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/v1/
`backend/config/urls.py` declares `ANY /api/v1/` 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: ANY /auth/
`backend/config/urls.py` declares `ANY /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: ANY /auth/change-email/
`backend/apps/users/urls.py` declares `ANY /auth/change-email/` 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: ANY /auth/change-email/confirm/
`backend/apps/users/urls.py` declares `ANY /auth/change-email/confirm/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /auth/change-password/
`backend/apps/users/urls.py` declares `ANY /auth/change-password/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /auth/invite-check/
`backend/apps/users/urls.py` declares `ANY /auth/invite-check/` 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: ANY /auth/login/
`backend/apps/users/urls.py` declares `ANY /auth/login/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /auth/logout/
`backend/apps/users/urls.py` declares `ANY /auth/logout/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /auth/me/
`backend/apps/users/urls.py` declares `ANY /auth/me/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /auth/register/
`backend/apps/users/urls.py` declares `ANY /auth/register/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /docs/
`backend/config/urls.py` declares `ANY /docs/` 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: ANY /feed/
`backend/config/urls.py` declares `ANY /feed/` 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: ANY /schema/
`backend/config/urls.py` declares `ANY /schema/` 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: ANY /search/
`backend/config/urls.py` declares `ANY /search/` 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: ANY /stats/
`backend/config/urls.py` declares `ANY /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
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/5238e3e4-a95f-4cef-b3e4-851f96a1841a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5238e3e4-a95f-4cef-b3e4-851f96a1841a/

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.