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

schmug/dmarcheck

https://github.com/schmug/dmarcheck · scanned 2026-06-16 00:04 UTC (2 months, 3 weeks ago)

258 raw signals (0 security + 258 graph)

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

Complete repo analysis

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

JSON
Combined
53.3
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 258 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 130 Medium 24 Low 55 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 258 Crowd 0 Layer: Frontend 5 Network 2 Security 7 Cicd 1 Quality 68 Api 175
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 53.3/100 with 100.0% coverage. It contains 1156 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 258 findings — concentrated in api (175), quality (68), security (7). Risk profile is high: 0 critical, 130 high, 24 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 209 of 258 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/callback (test/auth-routes.test.ts:88)
`test/auth-routes.test.ts:88` calls `GET /auth/callback` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/callback` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:21)
`test/auth-routes.test.ts:21` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:33)
`test/auth-routes.test.ts:33` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:41)
`test/auth-routes.test.ts:41` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:51)
`test/auth-routes.test.ts:51` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:59)
`test/auth-routes.test.ts:59` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/login (test/auth-routes.test.ts:67)
`test/auth-routes.test.ts:67` calls `GET /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/logout (test/auth-routes.test.ts:131)
`test/auth-routes.test.ts:131` calls `GET /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/logout (test/auth-routes.test.ts:141)
`test/auth-routes.test.ts:141` calls `GET /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:2332)
`test/dashboard-routes.test.ts:2332` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:2351)
`test/dashboard-routes.test.ts:2351` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:2390)
`test/dashboard-routes.test.ts:2390` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:2854)
`test/dashboard-routes.test.ts:2854` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:422)
`test/dashboard-routes.test.ts:422` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:455)
`test/dashboard-routes.test.ts:455` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:480)
`test/dashboard-routes.test.ts:480` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:491)
`test/dashboard-routes.test.ts:491` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:515)
`test/dashboard-routes.test.ts:515` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:550)
`test/dashboard-routes.test.ts:550` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:597)
`test/dashboard-routes.test.ts:597` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard (test/dashboard-routes.test.ts:666)
`test/dashboard-routes.test.ts:666` calls `GET /dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/portal (test/billing-routes.test.ts:530)
`test/billing-routes.test.ts:530` calls `GET /dashboard/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/portal` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/portal (test/billing-routes.test.ts:556)
`test/billing-routes.test.ts:556` calls `GET /dashboard/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/portal` If this points at an external API, prefix it with `https://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/portal (test/integration/stripe-lifecycle.test.ts:496)
`test/integration/stripe-lifecycle.test.ts:496` calls `GET /dashboard/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/portal` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/subscribe (test/billing-routes.test.ts:425)
`test/billing-routes.test.ts:425` calls `GET /dashboard/billing/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/subscribe` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/subscribe (test/billing-routes.test.ts:448)
`test/billing-routes.test.ts:448` calls `GET /dashboard/billing/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/subscribe` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/subscribe (test/billing-routes.test.ts:478)
`test/billing-routes.test.ts:478` calls `GET /dashboard/billing/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/subscribe` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/subscribe (test/integration/stripe-lifecycle.test.ts:343)
`test/integration/stripe-lifecycle.test.ts:343` calls `GET /dashboard/billing/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/subscribe` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/billing/subscribe (test/integration/stripe-lifecycle.test.ts:614)
`test/integration/stripe-lifecycle.test.ts:614` calls `GET /dashboard/billing/subscribe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/billing/subscribe` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/bulk (test/dashboard-routes.test.ts:2518)
`test/dashboard-routes.test.ts:2518` calls `GET /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/bulk (test/dashboard-routes.test.ts:2527)
`test/dashboard-routes.test.ts:2527` calls `GET /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/bulk (test/dashboard-routes.test.ts:2545)
`test/dashboard-routes.test.ts:2545` calls `GET /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/add (test/dashboard-routes.test.ts:1934)
`test/dashboard-routes.test.ts:1934` calls `GET /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/add (test/dashboard-routes.test.ts:1943)
`test/dashboard-routes.test.ts:1943` calls `GET /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/add (test/dashboard-routes.test.ts:2197)
`test/dashboard-routes.test.ts:2197` calls `GET /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/add (test/dashboard-routes.test.ts:2265)
`test/dashboard-routes.test.ts:2265` calls `GET /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com (test/dashboard-routes.test.ts:895)
`test/dashboard-routes.test.ts:895` calls `GET /dashboard/domain/example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com (test/dashboard-routes.test.ts:928)
`test/dashboard-routes.test.ts:928` calls `GET /dashboard/domain/example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com (test/dashboard-routes.test.ts:954)
`test/dashboard-routes.test.ts:954` calls `GET /dashboard/domain/example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com.json (test/dashboard-routes.test.ts:1001)
`test/dashboard-routes.test.ts:1001` calls `GET /dashboard/domain/example.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com.json` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com.json (test/dashboard-routes.test.ts:1078)
`test/dashboard-routes.test.ts:1078` calls `GET /dashboard/domain/example.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com.json` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com.json (test/dashboard-routes.test.ts:1157)
`test/dashboard-routes.test.ts:1157` calls `GET /dashboard/domain/example.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com.json` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com.json (test/dashboard-routes.test.ts:1212)
`test/dashboard-routes.test.ts:1212` calls `GET /dashboard/domain/example.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com.json` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com.json (test/dashboard-routes.test.ts:966)
`test/dashboard-routes.test.ts:966` calls `GET /dashboard/domain/example.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com.json` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1249)
`test/dashboard-routes.test.ts:1249` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1281)
`test/dashboard-routes.test.ts:1281` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1315)
`test/dashboard-routes.test.ts:1315` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1343)
`test/dashboard-routes.test.ts:1343` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1359)
`test/dashboard-routes.test.ts:1359` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/example.com/history (test/dashboard-routes.test.ts:1392)
`test/dashboard-routes.test.ts:1392` calls `GET /dashboard/domain/example.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/notmine.com (test/dashboard-routes.test.ts:904)
`test/dashboard-routes.test.ts:904` calls `GET /dashboard/domain/notmine.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/notmine.com` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/notmine.com.json (test/dashboard-routes.test.ts:975)
`test/dashboard-routes.test.ts:975` calls `GET /dashboard/domain/notmine.com.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/notmine.com.json` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domain/notmine.com/history (test/dashboard-routes.test.ts:1258)
`test/dashboard-routes.test.ts:1258` calls `GET /dashboard/domain/notmine.com/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/notmine.com/history` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domains (test/dashboard-routes.test.ts:767)
`test/dashboard-routes.test.ts:767` calls `GET /dashboard/domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domains` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domains (test/dashboard-routes.test.ts:789)
`test/dashboard-routes.test.ts:789` calls `GET /dashboard/domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domains` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domains (test/dashboard-routes.test.ts:824)
`test/dashboard-routes.test.ts:824` calls `GET /dashboard/domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domains` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/domains?q=alpha (test/dashboard-routes.test.ts:880)
`test/dashboard-routes.test.ts:880` calls `GET /dashboard/domains?q=alpha` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domains` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/export (test/dashboard-routes.test.ts:2640)
`test/dashboard-routes.test.ts:2640` calls `GET /dashboard/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/export` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/export (test/dashboard-routes.test.ts:2662)
`test/dashboard-routes.test.ts:2662` calls `GET /dashboard/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/export` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/export (test/dashboard-routes.test.ts:2707)
`test/dashboard-routes.test.ts:2707` calls `GET /dashboard/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/export` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/export (test/dashboard-routes.test.ts:2739)
`test/dashboard-routes.test.ts:2739` calls `GET /dashboard/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/export` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/export?format=json (test/dashboard-routes.test.ts:2799)
`test/dashboard-routes.test.ts:2799` calls `GET /dashboard/export?format=json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/export` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/home (test/auth-middleware.test.ts:22)
`test/auth-middleware.test.ts:22` calls `GET /dashboard/home` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/home` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/home (test/auth-middleware.test.ts:37)
`test/auth-middleware.test.ts:37` calls `GET /dashboard/home` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/home` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/home (test/auth-middleware.test.ts:55)
`test/auth-middleware.test.ts:55` calls `GET /dashboard/home` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/home` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1405)
`test/dashboard-routes.test.ts:1405` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1426)
`test/dashboard-routes.test.ts:1426` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1451)
`test/dashboard-routes.test.ts:1451` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1475)
`test/dashboard-routes.test.ts:1475` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1506)
`test/dashboard-routes.test.ts:1506` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings (test/dashboard-routes.test.ts:1517)
`test/dashboard-routes.test.ts:1517` calls `GET /dashboard/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings/api-keys (test/dashboard-routes.test.ts:1529)
`test/dashboard-routes.test.ts:1529` calls `GET /dashboard/settings/api-keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings/api-keys (test/dashboard-routes.test.ts:1562)
`test/dashboard-routes.test.ts:1562` calls `GET /dashboard/settings/api-keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings/api-keys (test/dashboard-routes.test.ts:1619)
`test/dashboard-routes.test.ts:1619` calls `GET /dashboard/settings/api-keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys` If this points at an external API, prefix it with `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard/settings/api-keys?created=1&raw=${encodeURIComponent(raw)} (test/dashboard-routes.test.ts:1591)
`test/dashboard-routes.test.ts:1591` calls `GET /dashboard/settings/api-keys?created=1&raw=${encodeURIComponent(raw)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys` If this poi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard?q=alpha (test/dashboard-routes.test.ts:717)
`test/dashboard-routes.test.ts:717` calls `GET /dashboard?q=alpha` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dashboard?q=zzz (test/dashboard-routes.test.ts:755)
`test/dashboard-routes.test.ts:755` calls `GET /dashboard?q=zzz` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /learn/${p.slug} (test/index.test.ts:875)
`test/index.test.ts:875` calls `GET /learn/${p.slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /learn/${p.slug} (test/index.test.ts:898)
`test/index.test.ts:898` calls `GET /learn/${p.slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/learn/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /legal (test/pricing-legal.test.ts:173)
`test/pricing-legal.test.ts:173` calls `GET /legal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/legal` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /legal/terms (test/pricing-legal.test.ts:168)
`test/pricing-legal.test.ts:168` calls `GET /legal/terms` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/legal/terms` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /mx/google (test/index.test.ts:1115)
`test/index.test.ts:1115` calls `GET /mx/google` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mx/google` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /public (test/auth-middleware.test.ts:65)
`test/auth-middleware.test.ts:65` calls `GET /public` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/public` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/alerts/1/acknowledge (test/dashboard-routes.test.ts:2403)
`test/dashboard-routes.test.ts:2403` calls `POST /dashboard/alerts/1/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/alerts/<p>/acknowledge` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/alerts/42/acknowledge (test/dashboard-routes.test.ts:2452)
`test/dashboard-routes.test.ts:2452` calls `POST /dashboard/alerts/42/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/alerts/<p>/acknowledge` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/alerts/99/acknowledge (test/dashboard-routes.test.ts:2495)
`test/dashboard-routes.test.ts:2495` calls `POST /dashboard/alerts/99/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/alerts/<p>/acknowledge` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/alerts/99999/acknowledge (test/dashboard-routes.test.ts:2506)
`test/dashboard-routes.test.ts:2506` calls `POST /dashboard/alerts/99999/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/alerts/<p>/acknowledge` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/alerts/abc/acknowledge (test/dashboard-routes.test.ts:2414)
`test/dashboard-routes.test.ts:2414` calls `POST /dashboard/alerts/abc/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/alerts/abc/acknowledge` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/bulk (test/dashboard-routes.test.ts:2560)
`test/dashboard-routes.test.ts:2560` calls `POST /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/bulk (test/dashboard-routes.test.ts:2569)
`test/dashboard-routes.test.ts:2569` calls `POST /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/bulk (test/dashboard-routes.test.ts:2595)
`test/dashboard-routes.test.ts:2595` calls `POST /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/bulk (test/dashboard-routes.test.ts:2622)
`test/dashboard-routes.test.ts:2622` calls `POST /dashboard/bulk` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/bulk` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:1957)
`test/dashboard-routes.test.ts:1957` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:1969)
`test/dashboard-routes.test.ts:1969` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:1988)
`test/dashboard-routes.test.ts:1988` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2030)
`test/dashboard-routes.test.ts:2030` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2054)
`test/dashboard-routes.test.ts:2054` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2086)
`test/dashboard-routes.test.ts:2086` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2125)
`test/dashboard-routes.test.ts:2125` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2162)
`test/dashboard-routes.test.ts:2162` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/add (test/dashboard-routes.test.ts:2229)
`test/dashboard-routes.test.ts:2229` calls `POST /dashboard/domain/add` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/add` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/example.com/delete (test/dashboard-routes.test.ts:2278)
`test/dashboard-routes.test.ts:2278` calls `POST /dashboard/domain/example.com/delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/delete` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/example.com/delete (test/dashboard-routes.test.ts:2290)
`test/dashboard-routes.test.ts:2290` calls `POST /dashboard/domain/example.com/delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/delete` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/example.com/scan (test/dashboard-routes.test.ts:1726)
`test/dashboard-routes.test.ts:1726` calls `POST /dashboard/domain/example.com/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/scan` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/example.com/scan (test/dashboard-routes.test.ts:1764)
`test/dashboard-routes.test.ts:1764` calls `POST /dashboard/domain/example.com/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/example.com/scan` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/domain/notmine.com/scan (test/dashboard-routes.test.ts:1737)
`test/dashboard-routes.test.ts:1737` calls `POST /dashboard/domain/notmine.com/scan` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/domain/notmine.com/scan` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/api-keys/generate (test/dashboard-routes.test.ts:1637)
`test/dashboard-routes.test.ts:1637` calls `POST /dashboard/settings/api-keys/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys/generate` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/api-keys/generate (test/dashboard-routes.test.ts:1650)
`test/dashboard-routes.test.ts:1650` calls `POST /dashboard/settings/api-keys/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys/generate` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/api-keys/generate (test/dashboard-routes.test.ts:1680)
`test/dashboard-routes.test.ts:1680` calls `POST /dashboard/settings/api-keys/generate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys/generate` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/api-keys/revoke (test/dashboard-routes.test.ts:1702)
`test/dashboard-routes.test.ts:1702` calls `POST /dashboard/settings/api-keys/revoke` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/api-keys/revoke` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/email-alerts (test/dashboard-routes.test.ts:1791)
`test/dashboard-routes.test.ts:1791` calls `POST /dashboard/settings/email-alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/email-alerts` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/email-alerts (test/dashboard-routes.test.ts:1804)
`test/dashboard-routes.test.ts:1804` calls `POST /dashboard/settings/email-alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/email-alerts` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/email-alerts (test/dashboard-routes.test.ts:1827)
`test/dashboard-routes.test.ts:1827` calls `POST /dashboard/settings/email-alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/email-alerts` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/webhook (test/dashboard-routes.test.ts:1848)
`test/dashboard-routes.test.ts:1848` calls `POST /dashboard/settings/webhook` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/webhook` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/webhook (test/dashboard-routes.test.ts:1864)
`test/dashboard-routes.test.ts:1864` calls `POST /dashboard/settings/webhook` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/webhook` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/webhook (test/dashboard-routes.test.ts:1890)
`test/dashboard-routes.test.ts:1890` calls `POST /dashboard/settings/webhook` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/webhook` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dashboard/settings/webhook (test/dashboard-routes.test.ts:1916)
`test/dashboard-routes.test.ts:1916` calls `POST /dashboard/settings/webhook` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dashboard/settings/webhook` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:160)
`test/billing-routes.test.ts:160` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:172)
`test/billing-routes.test.ts:172` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:211)
`test/billing-routes.test.ts:211` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:263)
`test/billing-routes.test.ts:263` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:300)
`test/billing-routes.test.ts:300` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:314)
`test/billing-routes.test.ts:314` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:344)
`test/billing-routes.test.ts:344` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/billing-routes.test.ts:368)
`test/billing-routes.test.ts:368` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/integration/stripe-lifecycle.test.ts:272)
`test/integration/stripe-lifecycle.test.ts:272` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/integration/stripe-lifecycle.test.ts:597)
`test/integration/stripe-lifecycle.test.ts:597` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /webhooks/stripe (test/integration/stripe-lifecycle.test.ts:627)
`test/integration/stripe-lifecycle.test.ts:627` calls `POST /webhooks/stripe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/webhooks/stripe` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.stripe.com/v1${path} (src/billing/stripe.ts:107)
`src/billing/stripe.ts:107` calls `POST https://api.stripe.com/v1${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stripe.com/v1/<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 https://api.workos.com/user_management/authenticate (src/auth/routes.ts:58)
`src/auth/routes.ts:58` calls `POST https://api.workos.com/user_management/authenticate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.workos.com/user_management/authenticate` If this points at an extern…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mta-sts-worker/src/index.ts:2
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/auth/routes.ts:58
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/billing/stripe.ts:107
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/views/scripts.ts:659
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — test/bearer-middleware.test.ts:58
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — test/bimi.test.ts:69
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — test/mta-sts.test.ts:236
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — test/rate-limit-middleware.test.ts:70
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 authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/dmarcus-mood-check/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/dmarcus-mood-check/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: src/db/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
src/db/CLAUDE.md VerificationClaude instruction
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/threat-model/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/skills/threat-model/SKILL.md:134 Supply chainClaude instruction
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 frontend Frontend quality conf 1.00 Custom React Flow node registered without explicit width/height — test/billing-routes.test.ts:357
When you register a custom node type via `nodeTypes`, the RFNode object you build must include `width` and `height` props. Without them, MiniMap renders ZERO mini-nodes for that type and `fitView` underestimates the bounds (cuts off lane labels, etc.). Add `width: …, height: …` to the node object. …
Fq rfnode no dims
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/index.ts:307
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/index.ts:307 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/views/scripts.ts:252
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/views/scripts.ts:252 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/views/html.ts:578
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/views/html.ts:578 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/views/scripts.ts:733
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/views/scripts.ts:733 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/release/check-releasable.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/release/check-releasable.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/routine-gate/github.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/routine-gate/github.ts:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 22 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/codeql.yml Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/codeql.yml Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 20 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 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 — scripts/release/check-releasable.ts:32
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/routine-gate/gate.ts:26
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 /_dev/dashboard
`src/index.ts` declares `GET /_dev/dashboard` 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/domain/:name/history
`src/index.ts` declares `GET /api/domain/:name/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /bulk
`src/dashboard/routes.ts` declares `GET /bulk` 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 /callback
`src/auth/routes.ts` declares `GET /callback` 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 /check
`src/index.ts` declares `GET /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: GET /check/score
`src/index.ts` declares `GET /check/score` 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 /domain/:domain
`src/dashboard/routes.ts` declares `GET /domain/:domain` 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 /domain/:domain/history
`src/dashboard/routes.ts` declares `GET /domain/:domain/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /domain/:domain{.+\\.json}
`src/dashboard/routes.ts` declares `GET /domain/:domain{.+\\.json}` 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 /domain/add
`src/dashboard/routes.ts` declares `GET /domain/add` 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 /domains
`src/dashboard/routes.ts` declares `GET /domains` 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 /export
`src/dashboard/routes.ts` declares `GET /export` 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 /login
`src/auth/routes.ts` declares `GET /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: GET /logout
`src/auth/routes.ts` declares `GET /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: GET /mx
`src/index.ts` declares `GET /mx` 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 /mx/:slug
`src/index.ts` declares `GET /mx/:slug` 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 /og-image.svg
`src/index.ts` declares `GET /og-image.svg` 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 /portal
`src/billing/routes.ts` declares `GET /portal` 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 /settings
`src/dashboard/routes.ts` declares `GET /settings` 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 /settings/api-keys
`src/dashboard/routes.ts` declares `GET /settings/api-keys` 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 /subscribe
`src/billing/routes.ts` declares `GET /subscribe` 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 /alerts/:id/acknowledge
`src/dashboard/routes.ts` declares `POST /alerts/:id/acknowledge` 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 /alerts/acknowledge-all
`src/dashboard/routes.ts` declares `POST /alerts/acknowledge-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bulk
`src/dashboard/routes.ts` declares `POST /bulk` 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 /domain/:domain/delete
`src/dashboard/routes.ts` declares `POST /domain/:domain/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: POST /domain/:domain/scan
`src/dashboard/routes.ts` declares `POST /domain/:domain/scan` 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 /domain/add
`src/dashboard/routes.ts` declares `POST /domain/add` 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 /mcp
`src/index.ts` declares `POST /mcp` 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 /settings/api-keys/generate
`src/dashboard/routes.ts` declares `POST /settings/api-keys/generate` 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 /settings/api-keys/revoke
`src/dashboard/routes.ts` declares `POST /settings/api-keys/revoke` 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 /settings/email-alerts
`src/dashboard/routes.ts` declares `POST /settings/email-alerts` 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 /settings/notify-on-change
`src/dashboard/routes.ts` declares `POST /settings/notify-on-change` 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 /settings/webhook
`src/dashboard/routes.ts` declares `POST /settings/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 /settings/webhook/test
`src/dashboard/routes.ts` declares `POST /settings/webhook/test` 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 /stripe
`src/billing/routes.ts` declares `POST /stripe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/*
`src/index.ts` declares `USE /api/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/bulk-scan
`src/index.ts` declares `USE /api/bulk-scan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/check
`src/index.ts` declares `USE /api/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: USE /api/check/stream
`src/index.ts` declares `USE /api/check/stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/domain/*
`src/index.ts` declares `USE /api/domain/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /badge
`src/index.ts` declares `USE /badge` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /check
`src/index.ts` declares `USE /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: USE /check/score
`src/index.ts` declares `USE /check/score` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /dashboard/*
`src/index.ts` declares `USE /dashboard/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /mcp
`src/index.ts` declares `USE /mcp` 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/index.ts (1535 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/views/dashboard.ts (3091 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/views/learn.ts (983 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/views/scripts.ts (1374 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/dashboard-routes.test.ts (2863 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/index.test.ts (1293 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/f9db8115-8e9e-4567-a433-7fd24ce46d5a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f9db8115-8e9e-4567-a433-7fd24ce46d5a/

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.