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

alexyordan1/ecco-facilities-website

https://github.com/alexyordan1/ecco-facilities-website · scanned 2026-06-17 01:32 UTC (1 month, 2 weeks ago)

80 raw signals (0 security + 80 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -11.0 (diff) · 80 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 74 of 80 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: GET /crm-leads?per_page=1&sort=created_at&order=desc (js/crm-core.js:340)
`js/crm-core.js:340` calls `GET /crm-leads?per_page=1&sort=created_at&order=desc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /crm-leads?per_page=500&sort=created_at&order=asc (js/crm-pipeline.js:38)
`js/crm-pipeline.js:38` calls `GET /crm-leads?per_page=500&sort=created_at&order=asc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /crm-leads?per_page=500&sort=created_at&order=desc (js/crm-reports.js:42)
`js/crm-reports.js:42` calls `GET /crm-leads?per_page=500&sort=created_at&order=desc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /crm-leads?stages=true (js/crm-detail.js:33)
`js/crm-detail.js:33` calls `GET /crm-leads?stages=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /crm-tags (js/crm-detail.js:36)
`js/crm-detail.js:36` calls `GET /crm-tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-tags` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /crm-tasks?upcoming=true&days=7 (js/crm-dashboard.js:109)
`js/crm-dashboard.js:109` calls `GET /crm-tasks?upcoming=true&days=7` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-tasks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-leads (js/crm-detail.js:820)
`js/crm-detail.js:820` calls `PATCH /crm-leads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-leads (js/crm-leads.js:277)
`js/crm-leads.js:277` calls `PATCH /crm-leads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-leads (js/crm-leads.js:299)
`js/crm-leads.js:299` calls `PATCH /crm-leads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-leads (js/crm-pipeline.js:151)
`js/crm-pipeline.js:151` calls `PATCH /crm-leads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-leads (js/crm-pipeline.js:224)
`js/crm-pipeline.js:224` calls `PATCH /crm-leads` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-leads` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /crm-tasks (js/crm-detail.js:785)
`js/crm-detail.js:785` calls `PATCH /crm-tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-tasks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/capture-partial (js/quote-flow.js:4850)
`js/quote-flow.js:4850` calls `POST /api/capture-partial` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/capture-partial` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/crm-auth (js/crm-auth.js:42)
`js/crm-auth.js:42` calls `POST /api/crm-auth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-auth` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/submit-quote (js/quote-flow.js:4516)
`js/quote-flow.js:4516` calls `POST /api/submit-quote` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/submit-quote` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-ai (js/crm-ai.js:117)
`js/crm-ai.js:117` calls `POST /crm-ai` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-ai` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-import (js/crm-leads.js:564)
`js/crm-leads.js:564` calls `POST /crm-import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-import` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-notes (js/crm-detail.js:593)
`js/crm-detail.js:593` calls `POST /crm-notes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-notes` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-notes (js/crm-detail.js:847)
`js/crm-detail.js:847` calls `POST /crm-notes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-notes` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-tags (js/crm-detail.js:702)
`js/crm-detail.js:702` calls `POST /crm-tags` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-tags` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /crm-tasks (js/crm-detail.js:642)
`js/crm-detail.js:642` calls `POST /crm-tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-tasks` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (functions/api/crm-ai.js:86)
`functions/api/crm-ai.js:86` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://github.com/login/oauth/access_token (functions/api/callback.js:9)
`functions/api/callback.js:9` calls `POST https://github.com/login/oauth/access_token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/github.com/login/oauth/access_token` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/crm-auth (js/crm-auth.js:100)
`js/crm-auth.js:100` calls `PUT /api/crm-auth` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crm-auth` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://aijgpluromciwgrbvhjq.supabase.co/auth/v1/user (js/crm-settings.js:69)
`js/crm-settings.js:69` calls `PUT https://aijgpluromciwgrbvhjq.supabase.co/auth/v1/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/aijgpluromciwgrbvhjq.supabase.co/auth/v1/user` If this points at an ext…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — functions/api/callback.js:9
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 — functions/api/capture-partial.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — functions/api/crm-leads.js:237
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 — functions/api/crm-notes.js:91
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 — functions/api/crm-tasks.js:36
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — functions/api/submit-quote.js:97
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 — js/crm-core.js:31
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 — js/crm-detail.js:32
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 — js/crm-leads.js:277
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 — js/quote-flow.js:4516
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in crm/reset-password.html:84
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
crm/reset-password.html:84 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/chat-widget.js:243
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/chat-widget.js:243 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/chat-widget.original.js:220
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/chat-widget.original.js:220 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/cookie-consent.js:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/cookie-consent.js:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-ai.js:10
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-ai.js:10 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-auth.js:108
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-auth.js:108 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-core.js:129
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-core.js:129 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-dashboard.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-dashboard.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-detail.js:78
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-detail.js:78 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-leads.js:86
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-leads.js:86 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-pipeline.js:107
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-pipeline.js:107 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/crm-reports.js:118
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/crm-reports.js:118 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/quote-flow.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/quote-flow.js:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in quote-dayporter.html:378
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
quote-dayporter.html:378 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in quote-janitorial.html:330
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
quote-janitorial.html:330 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in js/crm-core.js:132
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
js/crm-core.js:132 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in js/crm-detail.js:609
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
js/crm-detail.js:609 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in js/crm-leads.js:575
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
js/crm-leads.js:575 Insert adjacent html
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 35 placeholder/mock markers across 5 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 11 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 security security conf 1.00 Insecure pattern 'document_write' in js/crm-detail.js:198
Found a known-risky pattern (document_write). Review and replace if possible.
js/crm-detail.js:198 Document write
low System graph quality Tests conf 1.00 Low test-to-source ratio
8 tests / 38 src (ratio 0.21).
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: chat-backend/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
chat-backend/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: server/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `daysOld` in js/crm-core.js:426
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 `ecco_quote_draft_v1` in js/quote-flow.js:528
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 `ecco_quote_draft_v1` in tests/e2e/helpers.js: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 `eccoChatState_v1` in js/chat-widget.js:807
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — functions/api/submit-quote.js:602
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 — serve.js:37
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 — server/server.js:228
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 — tests/e2e/a11y-audit.spec.js:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`server/server.js` declares `GET /api/health` 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 /api/chat
`server/server.js` declares `POST /api/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 quality Complexity conf 1.00 Very large file: js/chat-widget.js (928 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: js/quote-flow.js (5435 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/d2385a96-f976-4584-addd-a7102d7620c2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d2385a96-f976-4584-addd-a7102d7620c2/

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.