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

verdeamokomatcha-code/sukomatcha

https://github.com/verdeamokomatcha-code/sukomatcha · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

136 raw signals (0 security + 136 graph)

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

Complete repo analysis

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

JSON
Combined
58.2
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 129 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 2 Medium 54 Low 63 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 129 Crowd 0 Layer: Frontend 31 Hardware 3 Security 23 Cicd 1 Quality 19 Api 52
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 58.2/100 with 100.0% coverage. It contains 1342 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 136 findings — concentrated in api (52), frontend (31), security (23). Risk profile is high: 0 critical, 2 high, 54 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.postalpincode.in/pincode/${pin} (frontend/customer/src/components/CartDrawer.tsx:279)
`frontend/customer/src/components/CartDrawer.tsx:279` calls `GET https://api.postalpincode.in/pincode/${pin}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.postalpincode.in/pincode/<p>` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://nominatim.openstreetmap.org/reverse?lat=${coords.latitude}&lon=${coords.longitude}&format=jsonv2&addressdetails=1&zoom=18 (frontend/customer/src/components/CartDrawer.tsx:472)
`frontend/customer/src/components/CartDrawer.tsx:472` calls `GET https://nominatim.openstreetmap.org/reverse?lat=${coords.latitude}&lon=${coords.longitude}&format=jsonv2&addressdetails=1&zoom=18` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalize…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/customer/src/app/bulk-orders/page.tsx:31
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/customer/src/app/buy-matcha-india/page.tsx:44
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/customer/src/app/ceremonial-matcha/page.tsx:42
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/customer/src/app/how-to-identify-fake-matcha/page.tsx:87
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/customer/src/app/how-to-make-matcha/page.tsx:43
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/customer/src/app/japanese-tea-rituals/page.tsx:42
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/customer/src/app/matcha-benefits/page.tsx:42
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/customer/src/app/matcha-for-focus/page.tsx:43
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/customer/src/app/matcha-guide/page.tsx:58
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/customer/src/app/matcha-latte-recipe/page.tsx:43
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/customer/src/app/matcha-vs-coffee/page.tsx:55
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/customer/src/app/matcha-vs-green-tea/page.tsx:42
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/customer/src/app/matcha-weight-loss/page.tsx:43
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/customer/src/app/page.tsx:17
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/customer/src/app/recipes/page.tsx:31
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/customer/src/app/reviews/page.tsx:18
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/customer/src/app/rituals/daily-focus/page.tsx:42
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/customer/src/app/shop/page.tsx:31
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/customer/src/app/story/page.tsx:31
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/customer/src/app/subscribe/page.tsx:31
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/customer/src/app/subscription/page.tsx:43
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/admin/src/app/(protected)/products/page.tsx:234
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 — frontend/admin/src/app/(protected)/recipes/page.tsx:153
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 — frontend/customer/src/components/CartDrawer.tsx:279
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 — frontend/customer/src/components/MatchaMoments.tsx:65
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 — frontend/customer/src/components/PremiumSections.tsx:1231
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 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 hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/bulk-orders/page.tsx:31
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/bulk-orders/page.tsx:31 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/buy-matcha-india/page.tsx:44
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/buy-matcha-india/page.tsx:44 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/ceremonial-matcha/page.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/ceremonial-matcha/page.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/how-to-identify-fake-matcha/page.tsx:87
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/how-to-identify-fake-matcha/page.tsx:87 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/how-to-make-matcha/page.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/how-to-make-matcha/page.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/japanese-tea-rituals/page.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/japanese-tea-rituals/page.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-benefits/page.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-benefits/page.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-for-focus/page.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-for-focus/page.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-guide/page.tsx:58
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-guide/page.tsx:58 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-latte-recipe/page.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-latte-recipe/page.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-vs-coffee/page.tsx:55
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-vs-coffee/page.tsx:55 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-vs-green-tea/page.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-vs-green-tea/page.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/matcha-weight-loss/page.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/matcha-weight-loss/page.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/page.tsx:17
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/page.tsx:17 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/recipes/page.tsx:31
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/recipes/page.tsx:31 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/reviews/page.tsx:18
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/reviews/page.tsx:18 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/rituals/daily-focus/page.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/rituals/daily-focus/page.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/shop/page.tsx:31
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/shop/page.tsx:31 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/story/page.tsx:31
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/story/page.tsx:31 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/subscribe/page.tsx:31
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/subscribe/page.tsx:31 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/customer/src/app/subscription/page.tsx:43
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/customer/src/app/subscription/page.tsx:43 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/admin/src/context/AuthContext.tsx:52
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/admin/src/context/AuthContext.tsx:52 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/customer/src/context/AuthContext.tsx:59
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/customer/src/context/AuthContext.tsx:59 Local storage auth token
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 170 placeholder/mock markers across 32 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
20 test file(s) for 285 source file(s) (ratio 0.07). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 13 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `CORS_ORIGINS`, `DELHIVERY_BASE_URL`, `DELHIVERY_PICKUP_LOCATION`, `DELHIVERY_TOKEN`, `DELHIVERY_WAREHOUSE_ADDRESS`, `DELHIVERY_WAREHOUSE_CITY`, `DELHIVERY_WAREHOUSE_NAME` + 5 more. Add them (with a placeholder/comment) to .env.example so onb…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 8 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 8 locations
frontend/admin/Dockerfile:2, 8, 19 (3 hits)
frontend/customer/Dockerfile:2, 8, 19 (3 hits)
backend/Dockerfile:2, 13 (2 hits)
containersPinned dependencies
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 Integrity conf 1.00 Old/deprecated-named symbol `suko_cart_v1` in frontend/customer/src/context/CartContext.tsx:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `suko_cart_v1` in tests/customer/checkout.spec.ts:37
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `suko_popup_seen_v1` in frontend/customer/src/components/EmailPopup.tsx:11
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 — tests/global.setup.ts:75
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 /cart/clear
`backend/src/modules/cart/cart.controller.ts` declares `DELETE /cart/clear` 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 /cart/item/:id
`backend/src/modules/cart/cart.controller.ts` declares `DELETE /cart/item/: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 /matcha-finder/goals/:id
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `DELETE /matcha-finder/goals/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /orders/:id/cancel
`backend/src/modules/orders/orders.controller.ts` declares `DELETE /orders/:id/cancel` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /popup-messages/:id
`backend/src/modules/popup-messages/popup-messages.controller.ts` declares `DELETE /popup-messages/: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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /reviews/:id
`backend/src/modules/reviews/reviews.controller.ts` declares `DELETE /reviews/: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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /users/addresses/:id
`backend/src/modules/users/users.controller.ts` declares `DELETE /users/addresses/: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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/google
`backend/src/modules/auth/auth.controller.ts` declares `GET /auth/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: GET /auth/google/callback
`backend/src/modules/auth/auth.controller.ts` declares `GET /auth/google/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auth/me
`frontend/customer/src/context/AuthContext.tsx` declares `GET /auth/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 /matcha-finder/config
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `GET /matcha-finder/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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /matcha-finder/experience-rules
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `GET /matcha-finder/experience-rules` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /matcha-finder/goals
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `GET /matcha-finder/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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /matcha-finder/stats
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `GET /matcha-finder/stats` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /orders/:id
`backend/src/modules/orders/orders.controller.ts` declares `GET /orders/: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 /reviews/admin
`backend/src/modules/reviews/reviews.controller.ts` declares `GET /reviews/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users/addresses
`backend/src/modules/users/users.controller.ts` declares `GET /users/addresses` 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 /users/profile
`backend/src/modules/users/users.controller.ts` declares `GET /users/profile` 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 /coupons/:id/toggle
`backend/src/modules/coupons/coupons.controller.ts` declares `PATCH /coupons/:id/toggle` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /matcha-finder/goals/:id
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `PATCH /matcha-finder/goals/: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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /popup-messages/:id
`backend/src/modules/popup-messages/popup-messages.controller.ts` declares `PATCH /popup-messages/: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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /recipes/:id
`backend/src/modules/recipes/recipes.controller.ts` declares `PATCH /recipes/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/setup
`frontend/admin/src/app/setup/page.tsx` declares `POST /admin/setup` 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 /admin/setup/forgot-password
`frontend/admin/src/app/login/page.tsx` declares `POST /admin/setup/forgot-password` 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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/shipping/schedule-pickup
`frontend/admin/src/app/(protected)/shipping/page.tsx` declares `POST /admin/shipping/schedule-pickup` 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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/forgot-password
`frontend/customer/src/components/AuthModal.tsx` declares `POST /auth/forgot-password` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/login
`frontend/customer/src/context/AuthContext.tsx` declares `POST /auth/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 /auth/register
`frontend/customer/src/context/AuthContext.tsx` declares `POST /auth/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 /auth/resend-verification
`frontend/customer/src/components/AuthModal.tsx` declares `POST /auth/resend-verification` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/reset-password
`frontend/customer/src/app/auth/reset-password/page.tsx` declares `POST /auth/reset-password` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/verify-email
`frontend/customer/src/components/AuthModal.tsx` declares `POST /auth/verify-email` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bulk-orders
`frontend/customer/src/components/BulkOrderForm.tsx` declares `POST /bulk-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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /cart/add
`backend/src/modules/cart/cart.controller.ts` declares `POST /cart/add` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /checkout
`frontend/customer/src/components/CartDrawer.tsx` 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 /coupons/validate
`frontend/customer/src/components/CartDrawer.tsx` declares `POST /coupons/validate` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /email-signup
`frontend/customer/src/components/EmailPopup.tsx` declares `POST /email-signup` 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 /matcha-finder/events
`frontend/customer/src/components/CartDrawer.tsx` declares `POST /matcha-finder/events` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /matcha-finder/goals
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `POST /matcha-finder/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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /matcha-finder/recommend
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `POST /matcha-finder/recommend` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /moments
`frontend/customer/src/components/PremiumSections.tsx` declares `POST /moments` 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 /orders/create
`backend/src/modules/orders/orders.controller.ts` declares `POST /orders/create` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /payments/verify
`frontend/customer/src/components/CartDrawer.tsx` declares `POST /payments/verify` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /reminders
`frontend/customer/src/components/PremiumSections.tsx` declares `POST /reminders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /reviews
`frontend/customer/src/components/PremiumSections.tsx` declares `POST /reviews` 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 /subscriptions
`frontend/customer/src/components/CartDrawer.tsx` declares `POST /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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/addresses
`backend/src/modules/users/users.controller.ts` declares `POST /users/addresses` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /cart/item/:id
`backend/src/modules/cart/cart.controller.ts` declares `PUT /cart/item/: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: PUT /matcha-finder/experience-rules
`backend/src/modules/matcha-finder/matcha-finder.controller.ts` declares `PUT /matcha-finder/experience-rules` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /users/addresses/:id/default
`backend/src/modules/users/users.controller.ts` declares `PUT /users/addresses/:id/default` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /users/profile
`backend/src/modules/users/users.controller.ts` declares `PUT /users/profile` 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: frontend/customer/src/components/CartDrawer.tsx (1254 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/customer/src/components/CustomerExperience.tsx (1369 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/customer/src/components/PremiumSections.tsx (2425 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/8fdbce01-22fb-4f4e-bb91-1224f795a1cc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8fdbce01-22fb-4f4e-bb91-1224f795a1cc/

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.