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

sambawy01/Holistic-Beauty-Website-

https://github.com/sambawy01/Holistic-Beauty-Website- · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

87 raw signals (0 security + 87 graph)

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

Complete repo analysis

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

JSON
Combined
50.5
/100
Security checks
51
0 findings
System graph
51
77.8% cov · 87 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 30 Medium 27 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 87 Crowd 0 Layer: Frontend 8 Network 3 Security 6 Quality 39 Api 31
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 50.5/100 with 77.8% coverage. It contains 1120 nodes across 5 cross-layer flows, written primarily in mixed languages. Engine surfaced 87 findings — concentrated in quality (39), api (31), frontend (8). Risk profile is high: 0 critical, 30 high, 27 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/catalog/${encodeURIComponent(product.slug)} (vercel-app/src/app/admin/products-section.tsx:521)
`vercel-app/src/app/admin/products-section.tsx:521` calls `DELETE /api/admin/catalog/${encodeURIComponent(product.slug)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/catalog/<p>` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/clients/${encodeURIComponent(clientId)} (vercel-app/src/app/admin/clients-section.tsx:291)
`vercel-app/src/app/admin/clients-section.tsx:291` calls `DELETE /api/admin/clients/${encodeURIComponent(clientId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/clients/${encodeURIComponent(clientId)} (vercel-app/src/app/admin/clients-section.tsx:712)
`vercel-app/src/app/admin/clients-section.tsx:712` calls `DELETE /api/admin/clients/${encodeURIComponent(clientId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/clients/${encodeURIComponent(clientId)}/note/${encodeURIComponent(noteId)} (vercel-app/src/app/admin/clients-section.tsx:225)
`vercel-app/src/app/admin/clients-section.tsx:225` calls `DELETE /api/admin/clients/${encodeURIComponent(clientId)}/note/${encodeURIComponent(noteId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/finance/${encodeURIComponent(entry.id)} (vercel-app/src/app/admin/finance-section.tsx:458)
`vercel-app/src/app/admin/finance-section.tsx:458` calls `DELETE /api/admin/finance/${encodeURIComponent(entry.id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/finance/<p>` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/clients${qs} (vercel-app/src/app/admin/clients-section.tsx:742)
`vercel-app/src/app/admin/clients-section.tsx:742` calls `GET /api/admin/clients${qs}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/clients/${encodeURIComponent(clientId)} (vercel-app/src/app/admin/clients-section.tsx:170)
`vercel-app/src/app/admin/clients-section.tsx:170` calls `GET /api/admin/clients/${encodeURIComponent(clientId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/clients/rebooking?weeks=${targetWeeks} (vercel-app/src/app/admin/clients-section.tsx:587)
`vercel-app/src/app/admin/clients-section.tsx:587` calls `GET /api/admin/clients/rebooking?weeks=${targetWeeks}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/rebooking` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/finance/${path}?month=${encodeURIComponent(month)} (vercel-app/src/app/admin/finance-section.tsx:589)
`vercel-app/src/app/admin/finance-section.tsx:589` calls `GET /api/admin/finance/${path}?month=${encodeURIComponent(month)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/finance/<p>` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/finance?month=${encodeURIComponent(targetMonth)} (vercel-app/src/app/admin/finance-section.tsx:550)
`vercel-app/src/app/admin/finance-section.tsx:550` calls `GET /api/admin/finance?month=${encodeURIComponent(targetMonth)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/finance` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/slots?${params} (vercel-app/src/app/admin/admin-inbox.tsx:234)
`vercel-app/src/app/admin/admin-inbox.tsx:234` calls `GET /api/admin/slots?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/slots` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/bookings/${booking.uid}/${action} (vercel-app/src/app/admin/admin-inbox.tsx:186)
`vercel-app/src/app/admin/admin-inbox.tsx:186` calls `POST /api/admin/bookings/${booking.uid}/${action}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/bookings/<p>/<p>` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/clients/${encodeURIComponent(clientId)}/note (vercel-app/src/app/admin/clients-section.tsx:198)
`vercel-app/src/app/admin/clients-section.tsx:198` calls `POST /api/admin/clients/${encodeURIComponent(clientId)}/note` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>/note` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/media (vercel-app/src/app/admin/finance-section.tsx:244)
`vercel-app/src/app/admin/finance-section.tsx:244` calls `POST /api/admin/media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/media` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/media (vercel-app/src/app/admin/products-section.tsx:162)
`vercel-app/src/app/admin/products-section.tsx:162` calls `POST /api/admin/media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/media` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/orders/${encodeURIComponent(order.orderNumber)}/status (vercel-app/src/app/admin/orders-section.tsx:195)
`vercel-app/src/app/admin/orders-section.tsx:195` calls `POST /api/admin/orders/${encodeURIComponent(order.orderNumber)}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/orders/<p>/status` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/booking-calendar/book (vercel-app/src/components/booking-calendar/booking-form/booking-form.tsx:121)
`vercel-app/src/components/booking-calendar/booking-form/booking-form.tsx:121` calls `POST /api/booking-calendar/book` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/booking-calendar/book` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/booking-calendar/cancel (vercel-app/src/components/booking-calendar/booking-widget.tsx:160)
`vercel-app/src/components/booking-calendar/booking-widget.tsx:160` calls `POST /api/booking-calendar/cancel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/booking-calendar/cancel` If this points at an external API…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/booking-calendar/reschedule (vercel-app/src/components/booking-calendar/booking-widget.tsx:205)
`vercel-app/src/components/booking-calendar/booking-widget.tsx:205` calls `POST /api/booking-calendar/reschedule` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/booking-calendar/reschedule` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/app/api/order/route.ts:339)
`vercel-app/src/app/api/order/route.ts:339` 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 `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/app/api/order/route.ts:404)
`vercel-app/src/app/api/order/route.ts:404` 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 `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/lib/assistant/tools.ts:1296)
`vercel-app/src/lib/assistant/tools.ts:1296` 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 …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/lib/booking-emails.ts:425)
`vercel-app/src/lib/booking-emails.ts:425` 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 `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/lib/daily-brief-email.ts:405)
`vercel-app/src/lib/daily-brief-email.ts:405` 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…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/lib/order-status-email.ts:330)
`vercel-app/src/lib/order-status-email.ts:330` 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 wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.resend.com/emails (vercel-app/src/lib/reports/shared.ts:334)
`vercel-app/src/lib/reports/shared.ts:334` 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 `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/catalog/${encodeURIComponent(product.slug)} (vercel-app/src/app/admin/products-section.tsx:418)
`vercel-app/src/app/admin/products-section.tsx:418` calls `PUT /api/admin/catalog/${encodeURIComponent(product.slug)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/catalog/<p>` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/catalog/${encodeURIComponent(product.slug)} (vercel-app/src/app/admin/products-section.tsx:489)
`vercel-app/src/app/admin/products-section.tsx:489` calls `PUT /api/admin/catalog/${encodeURIComponent(product.slug)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/catalog/<p>` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/clients/${encodeURIComponent(clientId)}/tags (vercel-app/src/app/admin/clients-section.tsx:246)
`vercel-app/src/app/admin/clients-section.tsx:246` calls `PUT /api/admin/clients/${encodeURIComponent(clientId)}/tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/clients/<p>/tags` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/treatments/${encodeURIComponent(treatment.slug)} (vercel-app/src/app/admin/treatments-section.tsx:279)
`vercel-app/src/app/admin/treatments-section.tsx:279` calls `PUT /api/admin/treatments/${encodeURIComponent(treatment.slug)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/treatments/<p>` If this points at an…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — shop.js:780
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 — vercel-app/scripts/setup-telegram.mjs:63
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 — vercel-app/src/app/admin/admin-inbox.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 — vercel-app/src/app/api/booking-calendar/book/route.ts:130
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 — vercel-app/src/app/api/booking-calendar/cancel/route.ts:51
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 — vercel-app/src/app/api/booking-calendar/reschedule/route.ts:53
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 — vercel-app/src/components/booking-calendar/booking-form/booking-form.tsx:121
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 — vercel-app/src/components/booking-calendar/booking-widget.tsx:205
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 — vercel-app/src/lib/assistant/tools.ts:1642
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 — vercel-app/src/lib/booking-calendar/hooks/use-calendar-slots.ts:129
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 — vercel-app/src/lib/booking-emails.ts:425
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 — vercel-app/src/lib/cal-slots.ts:74
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 — vercel-app/src/lib/telegram.ts:34
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 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chat.js:74
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chat.js:74 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in nav.js:44
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
nav.js:44 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in shop.js:556
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
shop.js:556 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in treatments.js:178
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
treatments.js:178 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in vercel-app/scripts/render-email-previews.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
vercel-app/scripts/render-email-previews.mjs:14 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 41 placeholder/mock markers across 15 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 18 in use
Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/cron-weekly-report.yml Ports
medium System graph network Security conf 1.00 Privileged port 20 in use
Port 20 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/cron-evening-digest.yml Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/keepalive.yml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 139 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_PASS`, `ADMIN_USER`, `GROQ_API_KEY`, `MEDIA_READ_WRITE_TOKEN`, `NODE_ENV`, `OLLAMA_MODEL_HEAVY`, `OLLAMA_MODEL_VISION`, `TEST_EVENT_TYPE_ID` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 72 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vercel-app/src/app/api/cal/webhook/route.ts:288
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 — vercel-app/src/app/api/order/route.ts:322
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 — vercel-app/src/lib/assistant/tools.ts:1281
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 — vercel-app/src/lib/booking-emails.ts:447
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 — vercel-app/src/lib/daily-brief-email.ts:393
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 — vercel-app/src/lib/order-status-email.ts:323
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 — vercel-app/src/lib/reports/shared.ts:314
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET
`vercel-app/src/lib/assistant/ollama-search.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 quality Complexity conf 1.00 Very large file: vercel-app/src/lib/assistant/tools.ts (1768 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/e5637950-3f7d-494c-9ffe-93e28274f391/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e5637950-3f7d-494c-9ffe-93e28274f391/

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.