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

SeedWebs/SeedOffice

https://github.com/SeedWebs/SeedOffice · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

193 raw signals (0 security + 193 graph)

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

Complete repo analysis

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

JSON
Combined
48.9
/100
Security checks
49
0 findings
System graph
49
88.9% cov · 193 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 97 Medium 17 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 193 Crowd 0 Layer: Frontend 20 Security 2 Quality 25 Api 146
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 48.9/100 with 88.9% coverage. It contains 1104 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 193 findings — concentrated in api (146), quality (25), frontend (20). Risk profile is high: 0 critical, 97 high, 17 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/docs/${a.id} (apps/api/test/docs.test.ts:67)
`apps/api/test/docs.test.ts:67` calls `DELETE /api/docs/${a.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/docs/<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: DELETE /api/groups/${g1.id} (apps/api/test/tasks.test.ts:94)
`apps/api/test/tasks.test.ts:94` calls `DELETE /api/groups/${g1.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/groups/<p>` 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: DELETE /api/inbox/clients/${client.id} (apps/api/test/inbox-settings.test.ts:113)
`apps/api/test/inbox-settings.test.ts:113` calls `DELETE /api/inbox/clients/${client.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/clients/<p>` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/inbox/clients/${client.id} (apps/api/test/inbox-settings.test.ts:122)
`apps/api/test/inbox-settings.test.ts:122` calls `DELETE /api/inbox/clients/${client.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/clients/<p>` If this points at an external API, prefix it with …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/time/${created.id} (apps/api/test/time.test.ts:139)
`apps/api/test/time.test.ts:139` calls `DELETE /api/time/${created.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/time/<p>` 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: DELETE /api/time/twa (apps/api/test/payroll-admin.test.ts:102)
`apps/api/test/payroll-admin.test.ts:102` calls `DELETE /api/time/twa` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/time/twa` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/payroll (apps/api/test/payroll-admin.test.ts:54)
`apps/api/test/payroll-admin.test.ts:54` calls `GET /api/admin/payroll` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/payroll` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/payroll/export?date=2026-06-10 (apps/api/test/payroll-admin.test.ts:75)
`apps/api/test/payroll-admin.test.ts:75` calls `GET /api/admin/payroll/export?date=2026-06-10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/payroll/export` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/payroll?date=2026-06-10 (apps/api/test/payroll-admin.test.ts:48)
`apps/api/test/payroll-admin.test.ts:48` calls `GET /api/admin/payroll?date=2026-06-10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/payroll` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/callback?code=c&state=WRONG (apps/api/test/auth.test.ts:161)
`apps/api/test/auth.test.ts:161` calls `GET /api/auth/callback?code=c&state=WRONG` 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://` …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/callback?code=test-code&state=st-123 (apps/api/test/auth.test.ts:107)
`apps/api/test/auth.test.ts:107` calls `GET /api/auth/callback?code=test-code&state=st-123` 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 `h…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/calendar-connect/connect (apps/api/test/gcal.test.ts:177)
`apps/api/test/gcal.test.ts:177` calls `GET /api/calendar-connect/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/calendar-connect/connect` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients/${cl.id} (apps/api/test/clients.test.ts:101)
`apps/api/test/clients.test.ts:101` calls `GET /api/clients/${cl.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients/${cl.id} (apps/api/test/clients.test.ts:89)
`apps/api/test/clients.test.ts:89` calls `GET /api/clients/${cl.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/docs/${root.id} (apps/api/test/docs.test.ts:36)
`apps/api/test/docs.test.ts:36` calls `GET /api/docs/${root.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/docs/<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 /api/expenses?month=2026-06 (apps/api/test/expenses.test.ts:55)
`apps/api/test/expenses.test.ts:55` calls `GET /api/expenses?month=2026-06` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/expenses?month=2026-06 (apps/api/test/expenses.test.ts:65)
`apps/api/test/expenses.test.ts:65` calls `GET /api/expenses?month=2026-06` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/attachments/${att.id}/download (apps/api/test/inbox-threads.test.ts:283)
`apps/api/test/inbox-threads.test.ts:283` calls `GET /api/inbox/attachments/${att.id}/download` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/attachments/<p>/download` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/attachments/${att.id}/download (apps/api/test/inbox-threads.test.ts:308)
`apps/api/test/inbox-threads.test.ts:308` calls `GET /api/inbox/attachments/${att.id}/download` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/attachments/<p>/download` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/google/callback?code=c&state=st-WRONG (apps/api/test/inbox-settings.test.ts:347)
`apps/api/test/inbox-settings.test.ts:347` calls `GET /api/inbox/google/callback?code=c&state=st-WRONG` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/google/callback` If this points at an external AP…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/google/callback?code=test-code&state=st-123 (apps/api/test/inbox-settings.test.ts:290)
`apps/api/test/inbox-settings.test.ts:290` calls `GET /api/inbox/google/callback?code=test-code&state=st-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/google/callback` If this points at an exter…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/mailboxes/${box.id}/connect (apps/api/test/inbox-settings.test.ts:221)
`apps/api/test/inbox-settings.test.ts:221` calls `GET /api/inbox/mailboxes/${box.id}/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/mailboxes/<p>/connect` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/mailboxes/${box.id}/connect (apps/api/test/inbox-settings.test.ts:248)
`apps/api/test/inbox-settings.test.ts:248` calls `GET /api/inbox/mailboxes/${box.id}/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/mailboxes/<p>/connect` If this points at an external API, p…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/mailboxes/xx/connect (apps/api/test/inbox-settings.test.ts:64)
`apps/api/test/inbox-settings.test.ts:64` calls `GET /api/inbox/mailboxes/xx/connect` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/mailboxes/xx/connect` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/search?q=${encodeURIComponent(long)} (apps/api/test/inbox-search.test.ts:182)
`apps/api/test/inbox-search.test.ts:182` calls `GET /api/inbox/search?q=${encodeURIComponent(long)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/search` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/search?q=test (apps/api/test/inbox-search.test.ts:208)
`apps/api/test/inbox-search.test.ts:208` calls `GET /api/inbox/search?q=test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/search` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/search?q=x (apps/api/test/inbox-search.test.ts:131)
`apps/api/test/inbox-search.test.ts:131` calls `GET /api/inbox/search?q=x` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/search` 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 /api/inbox/threads (apps/api/test/inbox-threads.test.ts:119)
`apps/api/test/inbox-threads.test.ts:119` calls `GET /api/inbox/threads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads (apps/api/test/inbox-threads.test.ts:139)
`apps/api/test/inbox-threads.test.ts:139` calls `GET /api/inbox/threads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads/${open.id} (apps/api/test/inbox-threads.test.ts:211)
`apps/api/test/inbox-threads.test.ts:211` calls `GET /api/inbox/threads/${open.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads/<p>` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads/${thread.id} (apps/api/test/inbox-extras.test.ts:104)
`apps/api/test/inbox-extras.test.ts:104` calls `GET /api/inbox/threads/${thread.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads/<p>` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads/${thread.id} (apps/api/test/inbox-extras.test.ts:86)
`apps/api/test/inbox-extras.test.ts:86` calls `GET /api/inbox/threads/${thread.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads/<p>` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads/${threadId} (apps/api/test/inbox-search.test.ts:246)
`apps/api/test/inbox-search.test.ts:246` calls `GET /api/inbox/threads/${threadId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads/<p>` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads?folder=all&q=ใบเสนอ (apps/api/test/inbox-threads.test.ts:185)
`apps/api/test/inbox-threads.test.ts:185` calls `GET /api/inbox/threads?folder=all&q=ใบเสนอ` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/inbox/threads?folder=mine (apps/api/test/inbox-threads.test.ts:162)
`apps/api/test/inbox-threads.test.ts:162` calls `GET /api/inbox/threads?folder=mine` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/inbox/threads` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/milestones/${ms.id} (apps/api/test/finance.test.ts:60)
`apps/api/test/finance.test.ts:60` calls `GET /api/milestones/${ms.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/milestones/<p>` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/payments/${created.id} (apps/api/test/clients.test.ts:42)
`apps/api/test/clients.test.ts:42` calls `GET /api/payments/${created.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/payments/<p>` 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 /api/payroll/u_nam (apps/api/test/payroll.test.ts:108)
`apps/api/test/payroll.test.ts:108` calls `GET /api/payroll/u_nam` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/payroll/u_nam` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id} (apps/api/test/projects.test.ts:72)
`apps/api/test/projects.test.ts:72` calls `GET /api/projects/${p.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/overview.test.ts:60)
`apps/api/test/overview.test.ts:60` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/tasks.test.ts:42)
`apps/api/test/tasks.test.ts:42` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/tasks.test.ts:48)
`apps/api/test/tasks.test.ts:48` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/tasks.test.ts:52)
`apps/api/test/tasks.test.ts:52` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/tasks.test.ts:78)
`apps/api/test/tasks.test.ts:78` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/board (apps/api/test/tasks.test.ts:90)
`apps/api/test/tasks.test.ts:90` calls `GET /api/projects/${p.id}/board` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/board` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/finance (apps/api/test/finance.test.ts:28)
`apps/api/test/finance.test.ts:28` calls `GET /api/projects/${p.id}/finance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/finance` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/finance (apps/api/test/finance.test.ts:31)
`apps/api/test/finance.test.ts:31` calls `GET /api/projects/${p.id}/finance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/finance` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/finance (apps/api/test/finance.test.ts:44)
`apps/api/test/finance.test.ts:44` calls `GET /api/projects/${p.id}/finance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/finance` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/finance (apps/api/test/finance.test.ts:61)
`apps/api/test/finance.test.ts:61` calls `GET /api/projects/${p.id}/finance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/finance` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/finance (apps/api/test/pnl.test.ts:68)
`apps/api/test/pnl.test.ts:68` calls `GET /api/projects/${p.id}/finance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/finance` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/pnl (apps/api/test/pnl.test.ts:39)
`apps/api/test/pnl.test.ts:39` calls `GET /api/projects/${p.id}/pnl` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/pnl` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/pnl (apps/api/test/pnl.test.ts:62)
`apps/api/test/pnl.test.ts:62` calls `GET /api/projects/${p.id}/pnl` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/pnl` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/pnl (apps/api/test/pnl.test.ts:71)
`apps/api/test/pnl.test.ts:71` calls `GET /api/projects/${p.id}/pnl` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/pnl` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects/${p.id}/pnl (apps/api/test/pnl.test.ts:82)
`apps/api/test/pnl.test.ts:82` calls `GET /api/projects/${p.id}/pnl` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/pnl` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id} (apps/api/test/task-detail.test.ts:90)
`apps/api/test/task-detail.test.ts:90` calls `GET /api/tasks/${t.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id} (apps/api/test/task-detail.test.ts:91)
`apps/api/test/task-detail.test.ts:91` calls `GET /api/tasks/${t.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id}/detail (apps/api/test/task-detail.test.ts:34)
`apps/api/test/task-detail.test.ts:34` calls `GET /api/tasks/${t.id}/detail` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/detail` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id}/detail (apps/api/test/task-detail.test.ts:93)
`apps/api/test/task-detail.test.ts:93` calls `GET /api/tasks/${t.id}/detail` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/detail` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id}/detail (apps/api/test/time.test.ts:60)
`apps/api/test/time.test.ts:60` calls `GET /api/tasks/${t.id}/detail` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/detail` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t.id}/time (apps/api/test/time.test.ts:116)
`apps/api/test/time.test.ts:116` calls `GET /api/tasks/${t.id}/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/time` 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 /api/tasks/${t.id}/time (apps/api/test/time.test.ts:156)
`apps/api/test/time.test.ts:156` calls `GET /api/tasks/${t.id}/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/time` 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 /api/tasks/${t.id}/time (apps/api/test/time.test.ts:56)
`apps/api/test/time.test.ts:56` calls `GET /api/tasks/${t.id}/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/time` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/tasks/${t1.id}/time (apps/api/test/time.test.ts:78)
`apps/api/test/time.test.ts:78` calls `GET /api/tasks/${t1.id}/time` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/time` 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 /api/team-hours (apps/api/test/integrity.test.ts:53)
`apps/api/test/integrity.test.ts:53` calls `GET /api/team-hours` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/team-hours` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/team-hours?date=2026-06-10 (apps/api/test/integrity.test.ts:40)
`apps/api/test/integrity.test.ts:40` calls `GET /api/team-hours?date=2026-06-10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/team-hours` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/team-hours?date=2026-06-10 (apps/api/test/integrity.test.ts:62)
`apps/api/test/integrity.test.ts:62` calls `GET /api/team-hours?date=2026-06-10` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/team-hours` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/time/${created.id} (apps/api/test/time.test.ts:131)
`apps/api/test/time.test.ts:131` calls `GET /api/time/${created.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/time/<p>` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/time/${manual.id} (apps/api/test/integrity.test.ts:37)
`apps/api/test/integrity.test.ts:37` calls `GET /api/time/${manual.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/time/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/time/twa (apps/api/test/payroll-admin.test.ts:101)
`apps/api/test/payroll-admin.test.ts:101` calls `GET /api/time/twa` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/time/twa` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/timer (apps/api/test/time.test.ts:49)
`apps/api/test/time.test.ts:49` calls `GET /api/timer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/timer` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/users/${u.id}/rates (apps/api/test/admin.test.ts:54)
`apps/api/test/admin.test.ts:54` calls `GET /api/users/${u.id}/rates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/<p>/rates` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/users/u_somchai/rates (apps/api/test/admin.test.ts:64)
`apps/api/test/admin.test.ts:64` calls `GET /api/users/u_somchai/rates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/u_somchai/rates` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /owner-only (apps/api/test/roles.test.ts:44)
`apps/api/test/roles.test.ts:44` calls `GET /owner-only` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/owner-only` 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: PATCH /api/expenses/${exp.id}/status (apps/api/test/expenses.test.ts:50)
`apps/api/test/expenses.test.ts:50` calls `PATCH /api/expenses/${exp.id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses/<p>/status` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/expenses/${target}/status (apps/api/test/expenses.test.ts:75)
`apps/api/test/expenses.test.ts:75` calls `PATCH /api/expenses/${target}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses/<p>/status` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/expenses?month=2026-06 (apps/api/test/expenses.test.ts:40)
`apps/api/test/expenses.test.ts:40` calls `PATCH /api/expenses?month=2026-06` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/expenses?month=2026-06 (apps/api/test/expenses.test.ts:51)
`apps/api/test/expenses.test.ts:51` calls `PATCH /api/expenses?month=2026-06` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/projects/${p.id} (apps/api/test/projects.test.ts:62)
`apps/api/test/projects.test.ts:62` calls `PATCH /api/projects/${p.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>` 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: POST /api/admin/users/${u.id}/rates (apps/api/test/admin.test.ts:43)
`apps/api/test/admin.test.ts:43` calls `POST /api/admin/users/${u.id}/rates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/users/<p>/rates` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/dev-login (apps/api/test/auth.test.ts:20)
`apps/api/test/auth.test.ts:20` calls `POST /api/auth/dev-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/dev-login` 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 /api/auth/dev-login (apps/api/test/auth.test.ts:35)
`apps/api/test/auth.test.ts:35` calls `POST /api/auth/dev-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/dev-login` 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 /api/auth/dev-login (apps/api/test/auth.test.ts:47)
`apps/api/test/auth.test.ts:47` calls `POST /api/auth/dev-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/dev-login` 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 /api/auth/dev-login (apps/api/test/auth.test.ts:59)
`apps/api/test/auth.test.ts:59` calls `POST /api/auth/dev-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/dev-login` 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 /api/auth/dev-login (apps/api/test/helpers.ts:37)
`apps/api/test/helpers.ts:37` calls `POST /api/auth/dev-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/dev-login` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/docs/images (apps/api/test/docs.test.ts:83)
`apps/api/test/docs.test.ts:83` calls `POST /api/docs/images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/docs/images` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/docs/images (apps/api/test/docs.test.ts:94)
`apps/api/test/docs.test.ts:94` calls `POST /api/docs/images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/docs/images` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/docs/images (apps/web/src/pages/Docs.tsx:36)
`apps/web/src/pages/Docs.tsx:36` calls `POST /api/docs/images` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/docs/images` 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/expenses (apps/api/test/expenses.test.ts:29)
`apps/api/test/expenses.test.ts:29` calls `POST /api/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/expenses (apps/api/test/expenses.test.ts:62)
`apps/api/test/expenses.test.ts:62` calls `POST /api/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/expenses (apps/api/test/expenses.test.ts:87)
`apps/api/test/expenses.test.ts:87` calls `POST /api/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/expenses (apps/web/src/pages/Expenses.tsx:67)
`apps/web/src/pages/Expenses.tsx:67` calls `POST /api/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/expenses` 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/expenses?month=2026-06 (apps/api/test/expenses.test.ts:79)
`apps/api/test/expenses.test.ts:79` calls `POST /api/expenses?month=2026-06` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/expenses` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/tasks/${t.id}/attachments (apps/api/test/task-detail.test.ts:47)
`apps/api/test/task-detail.test.ts:47` calls `POST /api/tasks/${t.id}/attachments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/attachments` 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 /api/tasks/${t.id}/attachments (apps/api/test/task-detail.test.ts:66)
`apps/api/test/task-detail.test.ts:66` calls `POST /api/tasks/${t.id}/attachments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/attachments` 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 /api/tasks/${t.id}/attachments (apps/api/test/task-detail.test.ts:75)
`apps/api/test/task-detail.test.ts:75` calls `POST /api/tasks/${t.id}/attachments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/tasks/<p>/attachments` 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 /api/tasks/${t.id}/attachments (apps/web/src/components/TaskDrawer.tsx:220)
`apps/web/src/components/TaskDrawer.tsx:220` calls `POST /api/tasks/${t.id}/attachments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tasks/<p>/attachments` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in worker-configuration.d.ts:3057
Found a known-risky pattern (exec_used). Review and replace if possible.
worker-configuration.d.ts:3057 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — apps/api/src/do/inbox-thread-hub.ts:16
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 — apps/api/src/do/presence-hub.ts:10
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 — apps/api/src/index.ts:127
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 — apps/api/src/lib/gcal-sync.ts:36
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 — apps/api/src/lib/inbox-sync.ts:46
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 — apps/api/src/routes/auth.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 — apps/api/src/routes/calendar-connect.ts:124
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 — apps/api/src/routes/inbox-settings.ts:322
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 — apps/api/src/routes/inbox-threads.ts:534
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 — apps/web/src/components/TaskDrawer.tsx:220
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 — apps/web/src/pages/Docs.tsx:36
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 — apps/web/src/pages/Expenses.tsx:67
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 — worker-configuration.d.ts:319
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 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 'direct_innerhtml_assignment' in mockup.html:850
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
mockup.html:850 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 59 placeholder/mock markers across 15 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/api/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.
apps/api/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/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.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/db/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.
packages/db/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `certIssuerDNLegacy` in worker-configuration.d.ts:11783
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 — apps/api/src/lib/backup.ts: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 — apps/api/src/lib/notify.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/api/src/lib/presence-notify.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 — worker-configuration.d.ts:186
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 /api/team-activity
`apps/web/src/components/TeamBox.tsx` declares `GET /api/team-activity` 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/users
`apps/web/src/components/TeamCalendar.tsx` declares `GET /api/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/admin/*
`apps/api/src/index.ts` declares `USE /api/admin/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/attachments/*
`apps/api/src/index.ts` declares `USE /api/attachments/*` 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/calendar
`apps/api/src/index.ts` declares `USE /api/calendar` 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/calendar-connect
`apps/api/src/index.ts` declares `USE /api/calendar-connect` 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/calendar-connect/*
`apps/api/src/index.ts` declares `USE /api/calendar-connect/*` 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/calendar/*
`apps/api/src/index.ts` declares `USE /api/calendar/*` 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/clients
`apps/api/src/index.ts` declares `USE /api/clients` 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/clients/*
`apps/api/src/index.ts` declares `USE /api/clients/*` 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/config
`apps/api/src/index.ts` declares `USE /api/config` 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/docs
`apps/api/src/index.ts` declares `USE /api/docs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/docs/*
`apps/api/src/index.ts` declares `USE /api/docs/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/expenses
`apps/api/src/index.ts` declares `USE /api/expenses` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/expenses/*
`apps/api/src/index.ts` declares `USE /api/expenses/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/groups/*
`apps/api/src/index.ts` declares `USE /api/groups/*` 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/inbox/attachments/*
`apps/api/src/index.ts` declares `USE /api/inbox/attachments/*` 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/inbox/canned
`apps/api/src/index.ts` declares `USE /api/inbox/canned` 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/inbox/canned/*
`apps/api/src/index.ts` declares `USE /api/inbox/canned/*` 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/inbox/clients
`apps/api/src/index.ts` declares `USE /api/inbox/clients` 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/inbox/clients/*
`apps/api/src/index.ts` declares `USE /api/inbox/clients/*` 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/inbox/compose
`apps/api/src/index.ts` declares `USE /api/inbox/compose` 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/inbox/google/*
`apps/api/src/index.ts` declares `USE /api/inbox/google/*` 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/inbox/import-thread
`apps/api/src/index.ts` declares `USE /api/inbox/import-thread` 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/inbox/mailboxes
`apps/api/src/index.ts` declares `USE /api/inbox/mailboxes` 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/inbox/mailboxes/*
`apps/api/src/index.ts` declares `USE /api/inbox/mailboxes/*` 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/inbox/search
`apps/api/src/index.ts` declares `USE /api/inbox/search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/inbox/settings
`apps/api/src/index.ts` declares `USE /api/inbox/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: USE /api/inbox/threads
`apps/api/src/index.ts` declares `USE /api/inbox/threads` 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/inbox/threads/*
`apps/api/src/index.ts` declares `USE /api/inbox/threads/*` 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/milestones/*
`apps/api/src/index.ts` declares `USE /api/milestones/*` 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/notes/*
`apps/api/src/index.ts` declares `USE /api/notes/*` 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/overview
`apps/api/src/index.ts` declares `USE /api/overview` 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/payments/*
`apps/api/src/index.ts` declares `USE /api/payments/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/payroll/*
`apps/api/src/index.ts` declares `USE /api/payroll/*` 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/projects
`apps/api/src/index.ts` declares `USE /api/projects` 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/projects/*
`apps/api/src/index.ts` declares `USE /api/projects/*` 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/projects/:id/finance
`apps/api/src/index.ts` declares `USE /api/projects/:id/finance` 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/projects/:id/milestones
`apps/api/src/index.ts` declares `USE /api/projects/:id/milestones` 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/projects/:id/payments
`apps/api/src/index.ts` declares `USE /api/projects/:id/payments` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/projects/:id/pnl
`apps/api/src/index.ts` declares `USE /api/projects/:id/pnl` 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/services/*
`apps/api/src/index.ts` declares `USE /api/services/*` 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/tasks/*
`apps/api/src/index.ts` declares `USE /api/tasks/*` 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/team-activity
`apps/api/src/index.ts` declares `USE /api/team-activity` 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/team-hours
`apps/api/src/index.ts` declares `USE /api/team-hours` 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/time/*
`apps/api/src/index.ts` declares `USE /api/time/*` 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/timer
`apps/api/src/index.ts` declares `USE /api/timer` 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/timer/*
`apps/api/src/index.ts` declares `USE /api/timer/*` 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/users
`apps/api/src/index.ts` declares `USE /api/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/users/*
`apps/api/src/index.ts` declares `USE /api/users/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: apps/web/src/pages/Inbox.tsx (1268 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker-configuration.d.ts (14497 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/0d0e718c-4ec6-48e4-950b-92928bea676b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0d0e718c-4ec6-48e4-950b-92928bea676b/

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.