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

sinapsioia/NEW-SINAPSIO

https://github.com/sinapsioia/NEW-SINAPSIO · scanned 2026-06-16 00:13 UTC (2 months, 2 weeks ago)

161 raw signals (0 security + 161 graph)

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

Complete repo analysis

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

JSON
Combined
52.5
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 157 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: layer: api × excluding tests × Reset all
Severity: Critical 0 High 39 Medium 40 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 157 Crowd 0 Layer: Frontend 7 Hardware 9 Cicd 1 Quality 51 Security 3 Api 86
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 52.5/100 with 100.0% coverage. It contains 1417 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 161 findings — concentrated in api (86), quality (52), hardware (12). Risk profile is high: 0 critical, 39 high, 41 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 86 of 157 actionable findings. 161 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds/${existing.sid}.json (apps/api/src/lib/twilioApi.ts:428)
`apps/api/src/lib/twilioApi.ts:428` calls `DELETE https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds/${existing.sid}.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/ap…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://www.googleapis.com/calendar/v3/calendars/primary/events/${encodeURIComponent(eventId)} (apps/api/src/lib/googleApi.ts:225)
`apps/api/src/lib/googleApi.ts:225` calls `DELETE https://www.googleapis.com/calendar/v3/calendars/primary/events/${encodeURIComponent(eventId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.mercadopago.com${path} (apps/api/src/lib/billing.ts:135)
`apps/api/src/lib/billing.ts:135` calls `GET https://api.mercadopago.com${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.mercadopago.com/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.telegram.org/bot${token}/getMe (apps/api/src/lib/channelRuntime.ts:1238)
`apps/api/src/lib/channelRuntime.ts:1238` calls `GET https://api.telegram.org/bot${token}/getMe` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/getme` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds.json?${params} (apps/api/src/lib/twilioApi.ts:403)
`apps/api/src/lib/twilioApi.ts:403` calls `GET https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds.json?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://r.jina.ai/${url} (apps/api/src/lib/scraper.ts:31)
`apps/api/src/lib/scraper.ts:31` calls `GET https://r.jina.ai/${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/r.jina.ai/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/calendar/v3/calendars/primary/events?${params.toString()} (apps/api/src/lib/googleApi.ts:177)
`apps/api/src/lib/googleApi.ts:177` calls `GET https://www.googleapis.com/calendar/v3/calendars/primary/events?${params.toString()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/calendar/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://api.elevenlabs.io/v1/convai/agents/${agentId} (apps/api/src/lib/elevenlabs.ts:112)
`apps/api/src/lib/elevenlabs.ts:112` calls `PATCH https://api.elevenlabs.io/v1/convai/agents/${agentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/convai/agents/<p>` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH https://www.googleapis.com/calendar/v3/calendars/primary/events/${encodeURIComponent(eventId)} (apps/api/src/lib/googleApi.ts:208)
`apps/api/src/lib/googleApi.ts:208` calls `PATCH https://www.googleapis.com/calendar/v3/calendars/primary/events/${encodeURIComponent(eventId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.c…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/convai/agents/${input.sourceAgentId}/duplicate (apps/api/src/lib/elevenlabs.ts:191)
`apps/api/src/lib/elevenlabs.ts:191` calls `POST https://api.elevenlabs.io/v1/convai/agents/${input.sourceAgentId}/duplicate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/convai/agents/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/convai/twilio/register-call (apps/api/src/lib/elevenlabs.ts:153)
`apps/api/src/lib/elevenlabs.ts:153` calls `POST https://api.elevenlabs.io/v1/convai/twilio/register-call` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/convai/twilio/register-call` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/agentCreator.ts:68)
`apps/api/src/lib/agentCreator.ts:68` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/agentSuggestion.ts:40)
`apps/api/src/lib/agentSuggestion.ts:40` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/assistantLlm.ts:37)
`apps/api/src/lib/assistantLlm.ts:37` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/callIntelligence.ts:59)
`apps/api/src/lib/callIntelligence.ts:59` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/channelRuntime.ts:365)
`apps/api/src/lib/channelRuntime.ts:365` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/lib/whatsappRuntime.ts:527)
`apps/api/src/lib/whatsappRuntime.ts:527` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openai.com/v1/chat/completions (apps/api/src/routes/ai.ts:45)
`apps/api/src/routes/ai.ts:45` calls `POST https://api.openai.com/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openai.com/v1/chat/completions` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${input.token}/sendMessage (apps/api/src/lib/channelRuntime.ts:766)
`apps/api/src/lib/channelRuntime.ts:766` calls `POST https://api.telegram.org/bot${input.token}/sendMessage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/sendmessage` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.telegram.org/bot${input.token}/setWebhook (apps/api/src/lib/channelRuntime.ts:1269)
`apps/api/src/lib/channelRuntime.ts:1269` calls `POST https://api.telegram.org/bot${input.token}/setWebhook` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.telegram.org/bot/<p>/setwebhook` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Calls.json (apps/api/src/lib/twilioApi.ts:330)
`apps/api/src/lib/twilioApi.ts:330` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Calls.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/accoun…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/IncomingPhoneNumbers.json (apps/api/src/lib/twilioApi.ts:163)
`apps/api/src/lib/twilioApi.ts:163` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/IncomingPhoneNumbers.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/20…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/IncomingPhoneNumbers/${incomingPhoneNumberSid}.json (apps/api/src/lib/twilioApi.ts:96)
`apps/api/src/lib/twilioApi.ts:96` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/IncomingPhoneNumbers/${incomingPhoneNumberSid}.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json (apps/api/src/lib/twilioApi.ts:206)
`apps/api/src/lib/twilioApi.ts:206` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/acc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json (apps/api/src/lib/twilioApi.ts:260)
`apps/api/src/lib/twilioApi.ts:260` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/acc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json (apps/api/src/lib/twilioApi.ts:294)
`apps/api/src/lib/twilioApi.ts:294` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/Messages.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/2010-04-01/acc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds.json (apps/api/src/lib/twilioApi.ts:373)
`apps/api/src/lib/twilioApi.ts:373` calls `POST https://api.twilio.com/2010-04-01/Accounts/${credentials.accountSid}/OutgoingCallerIds.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.twilio.com/2010-…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://comms.twilio.com/v1/Emails (apps/api/src/lib/email.ts:61)
`apps/api/src/lib/email.ts:61` calls `POST https://comms.twilio.com/v1/Emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/comms.twilio.com/v1/emails` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey} (apps/api/src/lib/assistantLlm.ts:60)
`apps/api/src/lib/assistantLlm.ts:60` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/generati…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey} (apps/api/src/lib/channelRuntime.ts:400)
`apps/api/src/lib/channelRuntime.ts:400` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/gener…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey} (apps/api/src/lib/whatsappRuntime.ts:490)
`apps/api/src/lib/whatsappRuntime.ts:490` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/gene…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey} (apps/api/src/lib/whatsappRuntime.ts:986)
`apps/api/src/lib/whatsappRuntime.ts:986` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${GEMINI_MODEL}:generateContent?key=${apiKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/gene…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.facebook.com/v20.0/${input.instagramAccountId}/messages (apps/api/src/lib/channelRuntime.ts:787)
`apps/api/src/lib/channelRuntime.ts:787` calls `POST https://graph.facebook.com/v20.0/${input.instagramAccountId}/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.facebook.com/v20.0/<p>/messages…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (apps/api/src/lib/googleApi.ts:27)
`apps/api/src/lib/googleApi.ts:27` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://sheets.googleapis.com/v4/spreadsheets/${input.spreadsheetId}/values/${encodeURIComponent(range)}:append?valueInputOption=USER_ENTERED (apps/api/src/lib/googleApi.ts:248)
`apps/api/src/lib/googleApi.ts:248` calls `POST https://sheets.googleapis.com/v4/spreadsheets/${input.spreadsheetId}/values/${encodeURIComponent(range)}:append?valueInputOption=USER_ENTERED` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized pat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://www.googleapis.com/calendar/v3/calendars/primary/events (apps/api/src/lib/googleApi.ts:148)
`apps/api/src/lib/googleApi.ts:148` calls `POST https://www.googleapis.com/calendar/v3/calendars/primary/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/calendar/v3/calendars/primary…
Dangling fetchFetch
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /products/:id
`apps/api/src/routes/catalog.ts` declares `DELETE /products/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`apps/api/src/routes/callerId.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /actions
`apps/api/src/routes/composio.ts` declares `GET /actions` 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 /connections
`apps/api/src/routes/composio.ts` declares `GET /connections` 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 /meta
`apps/api/src/routes/webhooks.ts` declares `GET /meta` 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 /orders
`apps/api/src/routes/catalog.ts` declares `GET /orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /products
`apps/api/src/routes/catalog.ts` declares `GET /products` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /subscription
`apps/api/src/routes/billing.ts` declares `GET /subscription` 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 /chat
`apps/api/src/routes/assistant.ts` declares `POST /chat` 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 /connect
`apps/api/src/routes/composio.ts` declares `POST /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: POST /create-checkout
`apps/api/src/routes/billing.ts` declares `POST /create-checkout` 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 /draft/apply
`apps/api/src/routes/assistant.ts` declares `POST /draft/apply` 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 /elevenlabs/post-call
`apps/api/src/routes/webhooks.ts` declares `POST /elevenlabs/post-call` 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 /elevenlabs/tool
`apps/api/src/routes/webhooks.ts` declares `POST /elevenlabs/tool` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /generate-pitch-block
`apps/api/src/routes/ai.ts` declares `POST /generate-pitch-block` 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 /ingest
`services/rag/main.py` declares `POST /ingest` 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 /ingest-file
`services/rag/main.py` declares `POST /ingest-file` 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 /mercadopago
`apps/api/src/routes/webhooks.ts` declares `POST /mercadopago` 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 /meta
`apps/api/src/routes/webhooks.ts` declares `POST /meta` 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 /portal
`apps/api/src/routes/billing.ts` declares `POST /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: POST /products
`apps/api/src/routes/catalog.ts` declares `POST /products` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /property-inbox/:connectionId
`apps/api/src/routes/webhooks.ts` declares `POST /property-inbox/:connectionId` 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 /retrieve
`services/rag/main.py` declares `POST /retrieve` 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 /start
`apps/api/src/routes/callerId.ts` declares `POST /start` 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
`apps/api/src/routes/webhooks.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: POST /telegram/:connectionId
`apps/api/src/routes/webhooks.ts` declares `POST /telegram/:connectionId` 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 /twilio/status
`apps/api/src/routes/webhooks.ts` declares `POST /twilio/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /twilio/voice
`apps/api/src/routes/webhooks.ts` declares `POST /twilio/voice` 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 /twilio/whatsapp
`apps/api/src/routes/webhooks.ts` declares `POST /twilio/whatsapp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /products/:id
`apps/api/src/routes/catalog.ts` declares `PUT /products/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /agents
`apps/api/src/index.ts` declares `USE /agents` 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 /ai
`apps/api/src/index.ts` declares `USE /ai` 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 /assistant
`apps/api/src/index.ts` declares `USE /assistant` 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 /billing
`apps/api/src/index.ts` declares `USE /billing` 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 /bookings
`apps/api/src/index.ts` declares `USE /bookings` 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 /calls
`apps/api/src/index.ts` declares `USE /calls` 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 /catalog
`apps/api/src/index.ts` declares `USE /catalog` 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 /channels
`apps/api/src/index.ts` declares `USE /channels` 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 /composio
`apps/api/src/index.ts` declares `USE /composio` 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 /contacts
`apps/api/src/index.ts` declares `USE /contacts` 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 /conversations
`apps/api/src/index.ts` declares `USE /conversations` 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 /integrations
`apps/api/src/index.ts` declares `USE /integrations` 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 /knowledge
`apps/api/src/index.ts` declares `USE /knowledge` 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 /leads
`apps/api/src/index.ts` declares `USE /leads` 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 /notifications
`apps/api/src/index.ts` declares `USE /notifications` 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 /provision
`apps/api/src/index.ts` declares `USE /provision` 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 /tenant
`apps/api/src/index.ts` declares `USE /tenant` 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 /usage
`apps/api/src/index.ts` declares `USE /usage` 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 /webhooks
`apps/api/src/index.ts` declares `USE /webhooks` 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 /whatsapp
`apps/api/src/index.ts` declares `USE /whatsapp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/8639658c-8830-4b7a-965b-bee90bccc77c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8639658c-8830-4b7a-965b-bee90bccc77c/

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.