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

sebastian-skipwith/ledger

https://github.com/sebastian-skipwith/ledger · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

101 raw signals (0 security + 101 graph)

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

Complete repo analysis

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

JSON
Combined
49.2
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 100 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 21 Medium 14 Low 60 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 100 Crowd 0 Layer: Frontend 6 Security 4 Cicd 3 Quality 16 Api 71
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 49.2/100 with 100.0% coverage. It contains 317 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 101 findings — concentrated in api (71), quality (16), frontend (6). Risk profile is high: 0 critical, 21 high, 15 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/account (frontend/components/Sidebar.tsx:24)
`frontend/components/Sidebar.tsx:24` calls `DELETE /api/account` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/account` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/developer/keys/${id} (frontend/app/developers/page.tsx:29)
`frontend/app/developers/page.tsx:29` calls `DELETE /api/developer/keys/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/developer/keys/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/account/export (frontend/components/Sidebar.tsx:9)
`frontend/components/Sidebar.tsx:9` calls `GET /api/account/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/account/export` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/accounts (frontend/app/page.tsx:26)
`frontend/app/page.tsx:26` calls `GET /api/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/accounts` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/metrics (frontend/app/admin/page.tsx:15)
`frontend/app/admin/page.tsx:15` calls `GET /api/admin/metrics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/admin/metrics` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ai/insights (frontend/app/page.tsx:27)
`frontend/app/page.tsx:27` calls `GET /api/ai/insights` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/ai/insights` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/developer/keys (frontend/app/developers/page.tsx:16)
`frontend/app/developers/page.tsx:16` calls `GET /api/developer/keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/developer/keys` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/intelligence/alerts (frontend/components/IntelligencePanel.tsx:16)
`frontend/components/IntelligencePanel.tsx:16` calls `GET /api/intelligence/alerts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/intelligence/alerts` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/intelligence/cash-flow (frontend/components/IntelligencePanel.tsx:15)
`frontend/components/IntelligencePanel.tsx:15` calls `GET /api/intelligence/cash-flow` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/intelligence/cash-flow` If this points at an external API, prefix it wit…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/intelligence/subscriptions (frontend/components/IntelligencePanel.tsx:14)
`frontend/components/IntelligencePanel.tsx:14` calls `GET /api/intelligence/subscriptions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/intelligence/subscriptions` If this points at an external API, prefi…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/net-worth?days=120 (frontend/app/page.tsx:35)
`frontend/app/page.tsx:35` calls `GET /api/net-worth?days=120` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/net-worth` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/summary/hud (frontend/app/page.tsx:28)
`frontend/app/page.tsx:28` calls `GET /api/summary/hud` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/summary/hud` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/${mode} (frontend/app/page.tsx:173)
`frontend/app/page.tsx:173` calls `POST /api/auth/${mode}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/google (frontend/app/page.tsx:136)
`frontend/app/page.tsx:136` calls `POST /api/auth/google` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/auth/google` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/checkout (frontend/components/Sidebar.tsx:32)
`frontend/components/Sidebar.tsx:32` calls `POST /api/billing/checkout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/billing/checkout` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/billing/portal (frontend/components/Sidebar.tsx:43)
`frontend/components/Sidebar.tsx:43` calls `POST /api/billing/portal` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/billing/portal` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/developer/keys (frontend/app/developers/page.tsx:22)
`frontend/app/developers/page.tsx:22` calls `POST /api/developer/keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/developer/keys` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/intelligence/categorize (frontend/components/IntelligencePanel.tsx:21)
`frontend/components/IntelligencePanel.tsx:21` calls `POST /api/intelligence/categorize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/intelligence/categorize` If this points at an external API, prefix it …
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/plaid/create-link-token (frontend/components/PlaidLink.tsx:17)
`frontend/components/PlaidLink.tsx:17` calls `POST /api/plaid/create-link-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/plaid/create-link-token` If this points at an external API, prefix it with `ht…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/plaid/exchange-token (frontend/components/PlaidLink.tsx:29)
`frontend/components/PlaidLink.tsx:29` calls `POST /api/plaid/exchange-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/plaid/exchange-token` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (backend/src/lib/email.js:9)
`backend/src/lib/email.js:9` calls `POST https://api.resend.com/emails` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.resend.com/emails` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/app/layout.tsx:23
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/components/AiChat.tsx:177
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/lib/store.ts:133
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 — mcp-server/src/index.js: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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests. 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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 23, 37
.github/workflows/release.yml:23, 37 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/app/layout.tsx:23
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/app/layout.tsx:23 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/components/AiChat.tsx:177
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/components/AiChat.tsx:177 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in desktop-bar/ui/index.html:282
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
desktop-bar/ui/index.html:282 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in desktop-bar/ui/login.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
desktop-bar/ui/login.js:37 Direct innerhtml assignment
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 47 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 15 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_EMAILS`, `APP_URL`, `DATA_ENCRYPTION_KEY`, `EMAIL_FROM`, `GOOGLE_CLIENT_ID`, `LEDGER_REFRESH_TOKEN`, `NEXT_PUBLIC_API_URL`, `NEXT_PUBLIC_GOOGLE_CLIENT_ID` + 7 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't …
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 5 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:20 CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality 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 — backend/src/index.js:133
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/routes/plaid.js:216
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 — backend/src/routes/webhooks.js:25
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 — frontend/components/components.tsx:240
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: DELETE /
`backend/src/routes/account.js` declares `DELETE /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:id
`backend/src/routes/bills.js` declares `DELETE /: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: DELETE /items/:id
`backend/src/routes/plaid.js` declares `DELETE /items/: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: DELETE /keys/:id
`backend/src/routes/developer.js` declares `DELETE /keys/: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 /
`backend/src/routes/transactions.js` 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 /alerts
`backend/src/routes/intelligence.js` declares `GET /alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /cash-flow
`backend/src/routes/intelligence.js` declares `GET /cash-flow` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /export
`backend/src/routes/account.js` declares `GET /export` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /hud
`backend/src/routes/summary.js` declares `GET /hud` 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 /insights
`backend/src/routes/ai.js` declares `GET /insights` 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 /items
`backend/src/routes/plaid.js` declares `GET /items` 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 /keys
`backend/src/routes/developer.js` declares `GET /keys` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me
`backend/src/routes/auth.js` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sessions
`backend/src/routes/ai.js` declares `GET /sessions` 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 /sessions/:sessionId
`backend/src/routes/ai.js` declares `GET /sessions/:sessionId` 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 /subscriptions
`backend/src/routes/intelligence.js` declares `GET /subscriptions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /summary
`backend/src/routes/transactions.js` declares `GET /summary` 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: PATCH /:id
`backend/src/routes/transactions.js` declares `PATCH /: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: POST /
`backend/src/routes/webhooks-stripe.js` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /alerts/:id/read
`backend/src/routes/intelligence.js` declares `POST /alerts/:id/read` 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 /categorize
`backend/src/routes/intelligence.js` declares `POST /categorize` 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
`backend/src/routes/ai.js` 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 /checkout
`backend/src/routes/billing.js` declares `POST /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 /create-link-token
`backend/src/routes/plaid.js` declares `POST /create-link-token` 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 /exchange-token
`backend/src/routes/plaid.js` declares `POST /exchange-token` 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 /google
`backend/src/routes/auth-google.js` declares `POST /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: POST /keys
`backend/src/routes/developer.js` declares `POST /keys` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`backend/src/routes/auth.js` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /plaid
`backend/src/routes/webhooks.js` declares `POST /plaid` 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
`backend/src/routes/billing.js` 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 /refresh
`backend/src/routes/auth.js` declares `POST /refresh` 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 /register
`backend/src/routes/auth.js` declares `POST /register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /sync
`backend/src/routes/plaid.js` declares `POST /sync` 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/account
`backend/src/index.js` declares `USE /api/account` 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/accounts
`backend/src/index.js` declares `USE /api/accounts` 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
`backend/src/index.js` 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/ai
`backend/src/index.js` declares `USE /api/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 /api/auth
`backend/src/index.js` declares `USE /api/auth` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/billing
`backend/src/index.js` declares `USE /api/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 /api/bills
`backend/src/index.js` declares `USE /api/bills` 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/developer
`backend/src/index.js` declares `USE /api/developer` 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/goals
`backend/src/index.js` declares `USE /api/goals` 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/intelligence
`backend/src/index.js` declares `USE /api/intelligence` 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/mcp
`backend/src/index.js` declares `USE /api/mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/net-worth
`backend/src/index.js` declares `USE /api/net-worth` 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/plaid
`backend/src/index.js` declares `USE /api/plaid` 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/summary
`backend/src/index.js` declares `USE /api/summary` 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/transactions
`backend/src/index.js` declares `USE /api/transactions` 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/webhooks
`backend/src/index.js` declares `USE /api/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 /api/webhooks/stripe
`backend/src/index.js` declares `USE /api/webhooks/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
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/afd657eb-1e4e-4334-9d75-c728f723f112/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/afd657eb-1e4e-4334-9d75-c728f723f112/

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.