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

satemafac/njangi-on-chain

https://github.com/satemafac/njangi-on-chain · scanned 2026-06-16 00:03 UTC (2 months, 3 weeks ago)

315 raw signals (0 security + 315 graph)

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

Complete repo analysis

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

JSON
Combined
46.9
/100
Security checks
47
0 findings
System graph
47
100.0% cov · 311 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 90 Medium 34 Low 94 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 311 Crowd 0 Layer: Frontend 75 Hardware 2 Security 11 Cicd 1 Quality 123 Api 99
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 46.9/100 with 100.0% coverage. It contains 2582 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 315 findings — concentrated in quality (123), api (99), frontend (75). Risk profile is high: 0 critical, 90 high, 34 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 218 of 311 actionable findings. 315 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: GET /api/admin/notifications/recent?address=${encodeURIComponent(notificationAddress)}&limit=50 (src/pages/admin/compliance.tsx:265)
`src/pages/admin/compliance.tsx:265` calls `GET /api/admin/notifications/recent?address=${encodeURIComponent(notificationAddress)}&limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/notifications/recent`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/automation/dashboard (src/pages/automation/dashboard.tsx:31)
`src/pages/automation/dashboard.tsx:31` calls `GET /api/automation/dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/automation/dashboard` 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/billing/status (src/components/milestones/entitlement-preflight.ts:56)
`src/components/milestones/entitlement-preflight.ts:56` calls `GET /api/billing/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/status` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/billing/status (src/components/ui/Navbar.tsx:242)
`src/components/ui/Navbar.tsx:242` calls `GET /api/billing/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/status` 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/billing/status (src/lib/entitlement-gate.ts:356)
`src/lib/entitlement-gate.ts:356` calls `GET /api/billing/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/status` 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/billing/status (src/pages/pricing.tsx:124)
`src/pages/pricing.tsx:124` calls `GET /api/billing/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/status` 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/circle-stats (src/pages/index.tsx:340)
`src/pages/index.tsx:340` calls `GET /api/circle-stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/circle-stats` 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/circles/swap-config?${queryParams} (src/services/swap-service.ts:74)
`src/services/swap-service.ts:74` calls `GET /api/circles/swap-config?${queryParams}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/circles/swap-config` 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/compliance/queue (src/pages/admin/compliance.tsx:146)
`src/pages/admin/compliance.tsx:146` calls `GET /api/compliance/queue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/compliance/queue` 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/join-requests/check?circleId=${id}&userAddress=${userAddress} (src/pages/circle/[id]/join/index.tsx:480)
`src/pages/circle/[id]/join/index.tsx:480` calls `GET /api/join-requests/check?circleId=${id}&userAddress=${userAddress}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/check` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/join-requests/pending/${id} (src/pages/circle/[id]/manage/index.tsx:1592)
`src/pages/circle/[id]/manage/index.tsx:1592` calls `GET /api/join-requests/pending/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/pending/<p>` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/join-requests/pending/mock-circle-1?clear=all (src/components/ui/Navbar.tsx:198)
`src/components/ui/Navbar.tsx:198` calls `GET /api/join-requests/pending/mock-circle-1?clear=all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/pending/mock-circle-1` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/legal/doc?doc=risk (src/components/LegalAcceptanceModal.tsx:200)
`src/components/LegalAcceptanceModal.tsx:200` calls `GET /api/legal/doc?doc=risk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/legal/doc` 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: GET /api/legal/status (src/components/LegalAcceptanceModal.tsx:498)
`src/components/LegalAcceptanceModal.tsx:498` calls `GET /api/legal/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/legal/status` 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/onramp/coinbase/options?${params.toString()} (src/components/CoinbaseOnrampLauncher.tsx:134)
`src/components/CoinbaseOnrampLauncher.tsx:134` calls `GET /api/onramp/coinbase/options?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/onramp/coinbase/options` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/whatsapp/admin-link-circle?circleId=${circleId}&network=${currentNetwork} (src/components/WhatsAppCircleIntegration.tsx:137)
`src/components/WhatsAppCircleIntegration.tsx:137` calls `GET /api/whatsapp/admin-link-circle?circleId=${circleId}&network=${currentNetwork}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/admin-link-circle…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/compliance/stale (src/pages/admin/compliance.tsx:226)
`src/pages/admin/compliance.tsx:226` calls `POST /api/admin/compliance/stale` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/compliance/stale` 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/automation/start (src/pages/_app.tsx:72)
`src/pages/_app.tsx:72` calls `POST /api/automation/start` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/automation/start` 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/billing/checkout-session (src/pages/pricing.tsx:146)
`src/pages/pricing.tsx:146` calls `POST /api/billing/checkout-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/checkout-session` 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/billing/portal-session (src/pages/pricing.tsx:176)
`src/pages/pricing.tsx:176` calls `POST /api/billing/portal-session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/billing/portal-session` 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/circles/swap-config (src/components/StablecoinSwapForm.tsx:110)
`src/components/StablecoinSwapForm.tsx:110` calls `POST /api/circles/swap-config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/circles/swap-config` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/compliance/prepare-issuance (src/pages/admin/compliance.tsx:309)
`src/pages/admin/compliance.tsx:309` calls `POST /api/compliance/prepare-issuance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/compliance/prepare-issuance` 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/compliance/queue (src/pages/admin/compliance.tsx:186)
`src/pages/admin/compliance.tsx:186` calls `POST /api/compliance/queue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/compliance/queue` 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: POST /api/compliance/queue (src/pages/admin/compliance.tsx:360)
`src/pages/admin/compliance.tsx:360` calls `POST /api/compliance/queue` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/compliance/queue` 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: POST /api/faucet/drip (src/pages/dashboard.tsx:2161)
`src/pages/dashboard.tsx:2161` calls `POST /api/faucet/drip` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/faucet/drip` 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/join-requests/${request.circle_id}/update (src/pages/circle/[id]/manage/index.tsx:2120)
`src/pages/circle/[id]/manage/index.tsx:2120` calls `POST /api/join-requests/${request.circle_id}/update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/<p>/update` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/join-requests/${request.circle_id}/update (src/pages/circle/[id]/manage/index.tsx:2246)
`src/pages/circle/[id]/manage/index.tsx:2246` calls `POST /api/join-requests/${request.circle_id}/update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/<p>/update` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/join-requests/${request.circle_id}/update (src/pages/circle/[id]/manage/index.tsx:2304)
`src/pages/circle/[id]/manage/index.tsx:2304` calls `POST /api/join-requests/${request.circle_id}/update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/<p>/update` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/join-requests/${request.circle_id}/update (src/pages/circle/[id]/manage/index.tsx:2437)
`src/pages/circle/[id]/manage/index.tsx:2437` calls `POST /api/join-requests/${request.circle_id}/update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/<p>/update` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/join-requests/create (src/pages/circle/[id]/join/index.tsx:522)
`src/pages/circle/[id]/join/index.tsx:522` calls `POST /api/join-requests/create` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/join-requests/create` 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/legal/accept (src/components/LegalAcceptanceModal.tsx:292)
`src/components/LegalAcceptanceModal.tsx:292` calls `POST /api/legal/accept` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/legal/accept` 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/legal/data-deletion-request (src/pages/legal/data-deletion.tsx:145)
`src/pages/legal/data-deletion.tsx:145` calls `POST /api/legal/data-deletion-request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/legal/data-deletion-request` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mainnet-signup (src/pages/index.tsx:369)
`src/pages/index.tsx:369` calls `POST /api/mainnet-signup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mainnet-signup` 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/onramp/coinbase/session (src/hooks/useCoinbaseSession.ts:141)
`src/hooks/useCoinbaseSession.ts:141` calls `POST /api/onramp/coinbase/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/onramp/coinbase/session` 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/onramp/moonpay/session (src/components/MoonPayLauncher.tsx:44)
`src/components/MoonPayLauncher.tsx:44` calls `POST /api/onramp/moonpay/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/onramp/moonpay/session` 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/onramp/transak/session (src/components/TransakLauncher.tsx:46)
`src/components/TransakLauncher.tsx:46` calls `POST /api/onramp/transak/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/onramp/transak/session` 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/whatsapp/admin-link-circle (src/components/WhatsAppCircleIntegration.tsx:197)
`src/components/WhatsAppCircleIntegration.tsx:197` calls `POST /api/whatsapp/admin-link-circle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/admin-link-circle` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/whatsapp/admin-unlink-circle (src/components/WhatsAppCircleIntegration.tsx:255)
`src/components/WhatsAppCircleIntegration.tsx:255` calls `POST /api/whatsapp/admin-unlink-circle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/admin-unlink-circle` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/whatsapp/auth/notify (src/contexts/AuthContext.tsx:323)
`src/contexts/AuthContext.tsx:323` calls `POST /api/whatsapp/auth/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/auth/notify` 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/whatsapp/auth/notify (src/pages/auth/callback.tsx:150)
`src/pages/auth/callback.tsx:150` calls `POST /api/whatsapp/auth/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/auth/notify` 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/whatsapp/auth/notify (src/pages/auth/callback.tsx:207)
`src/pages/auth/callback.tsx:207` calls `POST /api/whatsapp/auth/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/auth/notify` 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/whatsapp/auth/notify (src/pages/auth/whatsapp.tsx:35)
`src/pages/auth/whatsapp.tsx:35` calls `POST /api/whatsapp/auth/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/auth/notify` 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/whatsapp/auth/notify (src/pages/auth/whatsapp.tsx:73)
`src/pages/auth/whatsapp.tsx:73` calls `POST /api/whatsapp/auth/notify` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/whatsapp/auth/notify` 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/zkLogin (src/components/SimplifiedSwapUI.tsx:1140)
`src/components/SimplifiedSwapUI.tsx:1140` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/components/SimplifiedSwapUI.tsx:652)
`src/components/SimplifiedSwapUI.tsx:652` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/components/SimplifiedSwapUI.tsx:850)
`src/components/SimplifiedSwapUI.tsx:850` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/contexts/AuthContext.tsx:371)
`src/contexts/AuthContext.tsx:371` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/contexts/AuthContext.tsx:477)
`src/contexts/AuthContext.tsx:477` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/contexts/AuthContext.tsx:533)
`src/contexts/AuthContext.tsx:533` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/lib/cetus-service.ts:144)
`src/lib/cetus-service.ts:144` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/lib/swap-service.ts:170)
`src/lib/swap-service.ts:170` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/contribute/index.tsx:2430)
`src/pages/circle/[id]/contribute/index.tsx:2430` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/contribute/index.tsx:2462)
`src/pages/circle/[id]/contribute/index.tsx:2462` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/contribute/index.tsx:2584)
`src/pages/circle/[id]/contribute/index.tsx:2584` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/contribute/index.tsx:3063)
`src/pages/circle/[id]/contribute/index.tsx:3063` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:1632)
`src/pages/circle/[id]/manage/index.tsx:1632` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:1709)
`src/pages/circle/[id]/manage/index.tsx:1709` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:1781)
`src/pages/circle/[id]/manage/index.tsx:1781` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:1912)
`src/pages/circle/[id]/manage/index.tsx:1912` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:2205)
`src/pages/circle/[id]/manage/index.tsx:2205` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:2945)
`src/pages/circle/[id]/manage/index.tsx:2945` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:3633)
`src/pages/circle/[id]/manage/index.tsx:3633` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:4086)
`src/pages/circle/[id]/manage/index.tsx:4086` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:4967)
`src/pages/circle/[id]/manage/index.tsx:4967` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/circle/[id]/manage/index.tsx:5069)
`src/pages/circle/[id]/manage/index.tsx:5069` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/pages/dashboard.tsx:2285)
`src/pages/dashboard.tsx:2285` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1068)
`src/services/zkLoginClient.ts:1068` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1171)
`src/services/zkLoginClient.ts:1171` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1257)
`src/services/zkLoginClient.ts:1257` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1330)
`src/services/zkLoginClient.ts:1330` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1379)
`src/services/zkLoginClient.ts:1379` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:1518)
`src/services/zkLoginClient.ts:1518` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:256)
`src/services/zkLoginClient.ts:256` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:287)
`src/services/zkLoginClient.ts:287` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:351)
`src/services/zkLoginClient.ts:351` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:421)
`src/services/zkLoginClient.ts:421` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:608)
`src/services/zkLoginClient.ts:608` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:705)
`src/services/zkLoginClient.ts:705` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:788)
`src/services/zkLoginClient.ts:788` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:872)
`src/services/zkLoginClient.ts:872` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:927)
`src/services/zkLoginClient.ts:927` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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/zkLogin (src/services/zkLoginClient.ts:982)
`src/services/zkLoginClient.ts:982` calls `POST /api/zkLogin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/zklogin` 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 https://graph.facebook.com/v23.0/${phoneNumberId}/messages (src/lib/whatsapp-notifier.ts:369)
`src/lib/whatsapp-notifier.ts:369` calls `POST https://graph.facebook.com/v23.0/${phoneNumberId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<p>/messages` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages (src/pages/api/whatsapp/webhook.ts:323)
`src/pages/api/whatsapp/webhook.ts:323` calls `POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages (src/pages/api/whatsapp/webhook.ts:377)
`src/pages/api/whatsapp/webhook.ts:377` calls `POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages (src/pages/api/whatsapp/webhook.ts:420)
`src/pages/api/whatsapp/webhook.ts:420` calls `POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages (src/pages/api/whatsapp/webhook.ts:460)
`src/pages/api/whatsapp/webhook.ts:460` calls `POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages (src/pages/api/whatsapp/webhook.ts:498)
`src/pages/api/whatsapp/webhook.ts:498` calls `POST https://graph.facebook.com/v23.0/${process.env.WHATSAPP_PHONE_NUMBER_ID}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v23.0/<…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in scripts/bootstrap-package.mjs:124
Found a known-risky pattern (exec_used). Review and replace if possible.
scripts/bootstrap-package.mjs:124 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/services/postgres-adapter.ts:168
Found a known-risky pattern (exec_used). Review and replace if possible.
src/services/postgres-adapter.ts:168 Exec used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/LegalAcceptanceModal.tsx:316
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/pages/circle/[id]/contribute/index.tsx:3798
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/pages/index.tsx:573
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/pages/legal/[doc].tsx:140
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 — scripts/bootstrap-package.mjs:151
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 — scripts/cycle-finalized-notifier.mjs:202
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 — scripts/stripe-bootstrap.mjs:123
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 — src/components/SimplifiedSwapUI.tsx:652
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 — src/components/StablecoinSwapForm.tsx:110
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 — src/components/WhatsAppCircleIntegration.tsx:137
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 — src/lib/cetus-service.ts:144
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 — src/lib/swap-service.ts:170
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 — src/pages/api/whatsapp/webhook.ts:377
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 — src/pages/auth/callback.tsx:150
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 — src/pages/circle/[id]/contribute/index.tsx:2430
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 — src/pages/circle/[id]/manage/index.tsx:1632
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 — src/pages/dashboard.tsx:2285
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 — src/services/circle-status.service.ts:394
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 — src/services/enokiZkLoginService.ts:306
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 — src/services/swap-service.ts:74
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 — src/services/zkLoginClient.ts:256
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 — whatsapp-bot-backend/src/services/cycle-reminder.service.ts:864
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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in index.ts:14
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
index.ts:14 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/services/persistent-salt-service.ts:107
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/services/persistent-salt-service.ts:107 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/LegalAcceptanceModal.tsx:316
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/LegalAcceptanceModal.tsx:316 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/circle/[id]/contribute/index.tsx:3798
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/pages/circle/[id]/contribute/index.tsx:3798 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/index.tsx:573
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/pages/index.tsx:573 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/legal/[doc].tsx:140
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/pages/legal/[doc].tsx:140 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/contexts/AuthContext.tsx:222
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/contexts/AuthContext.tsx:222 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bootstrap-package.mjs:30
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bootstrap-package.mjs:30 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in next.config.js:115
Found a known-risky pattern (weak_hash). Review and replace if possible.
next.config.js:115 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 83 placeholder/mock markers across 35 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 Integrity conf 1.00 71 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOW_LIVE`, `BILLING_WEBHOOK_URL`, `COINBASE_ONRAMP_API_BASE_URL`, `COINBASE_ONRAMP_JWT_EXPIRES_IN_SECONDS`, `COINBASE_ONRAMP_REQUEST_TIMEOUT_MS`, `COMPLIANCE_RATE_LIMIT`, `COMPLIANCE_RATE_LIMIT_WINDOW_MS`, `ENABLE_EVENT_LISTENER` + 63 more. Add …
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1084 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 hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:18-alpine3.19
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 3 locations
whatsapp-bot-backend/Dockerfile:4, 29 (2 hits)
Dockerfile:1
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 17, 20, 27
.github/workflows/preflight.yml:17, 20, 27 (3 hits)
CI/CD securitySupply chainGithub actions
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: whatsapp-bot-backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
whatsapp-bot-backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `canonicalOrLegacy` in scripts/validate-env.mjs:37
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 `canonicalOrLegacy` in src/config/public-env.ts:113
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 `canonicalOrLegacy` in whatsapp-bot-backend/src/config/env.ts:44
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 `clob_v2` in src/services/constants.ts:19
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 `daysOld` in whatsapp-bot-backend/src/pages/api/whatsapp/webhook-handler.ts:297
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 `isRegistryDeprecated` in src/services/whatsapp-registry-service.ts:258
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 Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — index.ts:9
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 — scripts/migrate-postgres.js:45
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 — src/components/ActivityDetector.tsx: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 — src/components/IdleWarningModal.tsx:72
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 — src/components/InAppBrowserModal.tsx:184
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 — src/components/LoginButton.tsx:74
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 — src/components/SimplifiedSwapUI.tsx:65
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 — src/components/ui/Navbar.tsx:49
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 — src/components/WhatsAppCircleIntegration.tsx:235
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 — src/contexts/AuthContext.tsx:129
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 — src/lib/whatsapp-registry-init.ts:21
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 — src/pages/_app.tsx:64
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 — src/pages/api/auth/callback.ts:6
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 — src/pages/api/cetus-apr.ts:38
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 — src/pages/api/circle-stats.ts:110
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 — src/pages/api/join-requests/[circleId].ts:37
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 — src/pages/api/join-requests/[circleId]/update.ts:51
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 — src/pages/api/join-requests/check.ts:39
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 — src/pages/api/join-requests/create.ts:106
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 — src/pages/api/join-requests/lookup-user.ts:36
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 — src/pages/api/join-requests/pending/[circleId].ts:35
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 — src/pages/api/join-requests/user/[userAddress].ts:37
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 — src/pages/api/legal/data-deletion-request.ts:116
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 — src/pages/api/mainnet-signup.ts:108
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 — src/pages/api/whatsapp/admin-link-circle.ts:310
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 — src/pages/api/whatsapp/admin-unlink-circle.ts:67
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 — src/pages/api/zkLogin.ts:119
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 — src/pages/auth/callback.tsx:50
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 — src/pages/auth/whatsapp.tsx:50
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 — src/pages/callback.tsx:46
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 — src/pages/circle/[id]/contribute/index.tsx:572
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 — src/pages/circle/[id]/index.tsx:187
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 — src/pages/circle/[id]/join/index.tsx:106
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 — src/pages/circle/[id]/manage/index.tsx:107
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 — src/pages/create-circle.tsx:646
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 — src/pages/dashboard.tsx:103
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 — src/pages/index.tsx:415
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 — src/services/cetus-errors.ts:431
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 — src/services/cetus-service.ts:217
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 — src/services/circle-service.ts:280
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 — src/services/circle-status.service.ts:52
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 — src/services/enokiZkLoginService.ts:51
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 — src/services/join-request-database.ts:31
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 — src/services/join-request-service.ts:44
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 — src/services/mainnet-signup-database.ts:34
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 — src/services/network-config.ts:176
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 — src/services/persistent-salt-service.ts:133
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 — src/services/postgres-adapter.ts:81
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 — src/services/price-service.ts:132
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 — src/services/swap-service.ts:160
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 — src/services/whatsapp-registry-service.ts:87
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 — src/services/zkLoginClient.ts: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 — src/utils/logger.ts:7
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-cetus-pools.js:6
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 — whatsapp-bot-backend/src/config/config.ts:6
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 — whatsapp-bot-backend/src/services/whatsapp-sender.service.ts:162
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: GET /
`whatsapp-bot-backend/src/services/whatsapp-sender.service.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/status
`whatsapp-bot-backend/src/server.ts` declares `GET /api/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: GET /api/whatsapp/analytics
`whatsapp-bot-backend/src/server.ts` declares `GET /api/whatsapp/analytics` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/whatsapp/integration
`whatsapp-bot-backend/src/server.ts` declares `GET /api/whatsapp/integration` 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/whatsapp/queue
`whatsapp-bot-backend/src/server.ts` declares `GET /api/whatsapp/queue` 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/whatsapp/webhook
`whatsapp-bot-backend/src/server.ts` declares `GET /api/whatsapp/webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/whatsapp/send
`whatsapp-bot-backend/src/server.ts` declares `POST /api/whatsapp/send` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/whatsapp/webhook
`whatsapp-bot-backend/src/server.ts` declares `POST /api/whatsapp/webhook` 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 /generate-recovery-code
`src/services/persistent-salt-service.ts` declares `POST /generate-recovery-code` 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: POST /get-salt
`src/services/persistent-salt-service.ts` declares `POST /get-salt` 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 /recover-salt
`src/services/persistent-salt-service.ts` declares `POST /recover-salt` 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: src/components/SimplifiedSwapUI.tsx (2003 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/lib/i18n.ts (993 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/api/zkLogin.ts (6435 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/circle/[id]/contribute/index.tsx (4462 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/circle/[id]/index.tsx (1973 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/circle/[id]/join/index.tsx (1291 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/circle/[id]/manage/index.tsx (8366 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/create-circle.tsx (2715 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/dashboard.tsx (8730 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/index.tsx (1378 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/zkLoginClient.ts (1536 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: whatsapp-bot-backend/src/services/circle-link-listener.service.ts (3094 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/4dd67504-76cc-454d-a10f-a3a5dce2913b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4dd67504-76cc-454d-a10f-a3a5dce2913b/

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.