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

tcstulio/sistemav2

https://github.com/tcstulio/sistemav2 · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

373 raw signals (0 security + 373 graph)

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

Complete repo analysis

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

JSON
Combined
54.0
/100
Security checks
54
0 findings
System graph
54
100.0% cov · 298 findings
Critical
5
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 5 High 37 Medium 42 Low 133 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 298 Crowd 0 Layer: Frontend 128 Network 2 Hardware 1 Security 27 Quality 53 Api 87
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 54.0/100 with 100.0% coverage. It contains 3267 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 373 findings — concentrated in frontend (128), quality (128), api (87). Risk profile is high: 5 critical, 37 high, 117 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 214 of 298 actionable findings. 373 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.

critical System graph security Secrets conf 1.00 Possible secret in backend/src/scripts/debug-signature.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
backend/src/scripts/debug-signature.ts:5
critical System graph security Secrets conf 1.00 Possible secret in backend/src/scripts/debug-user-fields.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
backend/src/scripts/debug-user-fields.ts:7
critical System graph security Secrets conf 1.00 Possible secret in scripts/explore-all-pages.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/explore-all-pages.ts:20
critical System graph security Secrets conf 1.00 Possible secret in src/scripts/compare_tasks.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
src/scripts/compare_tasks.ts:9
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://localhost:${config.port}/api/dolibarr/thirdparties/${res.data} (backend/src/scripts/test-client-stripping.ts:42)
`backend/src/scripts/test-client-stripping.ts:42` calls `DELETE http://localhost:${config.port}/api/dolibarr/thirdparties/${res.data}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:/<p>/api/dolibarr…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/config/llm (src/components/DevelopmentConsole/LlmSettingsTab.tsx:110)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:110` calls `GET /api/admin/config/llm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm` If this points at an external API, prefix it with `https:…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/config/llm/models?provider=${targetProvider} (src/components/DevelopmentConsole/LlmSettingsTab.tsx:167)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:167` calls `GET /api/admin/config/llm/models?provider=${targetProvider}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/models` If this points a…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/config/llm/modules (src/components/DevelopmentConsole/LlmSettingsTab.tsx:132)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:132` calls `GET /api/admin/config/llm/modules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/modules` If this points at an external API, prefix…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/config/llm/prompts (src/components/DevelopmentConsole/LlmSettingsTab.tsx:143)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:143` calls `GET /api/admin/config/llm/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/prompts` If this points at an external API, prefix…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/config/llm/stats (src/components/DevelopmentConsole/LlmSettingsTab.tsx:154)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:154` calls `GET /api/admin/config/llm/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/stats` If this points at an external API, prefix it …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/status (src/components/AdminApp.tsx:41)
`src/components/AdminApp.tsx:41` calls `GET /api/admin/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/status` 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 /api/dashboard/artifacts (src/services/dashboardArtifacts.ts:16)
`src/services/dashboardArtifacts.ts:16` calls `GET /api/dashboard/artifacts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/dashboard/artifacts` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/github/issues/stats (src/services/githubService.ts:50)
`src/services/githubService.ts:50` calls `GET /api/github/issues/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/github/issues/stats` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/boleto (src/hooks/useItauBank.ts:156)
`src/hooks/useItauBank.ts:156` calls `GET /api/itau/boleto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/boleto` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/boleto/${nossoNumero} (src/hooks/useItauBank.ts:161)
`src/hooks/useItauBank.ts:161` calls `GET /api/itau/boleto/${nossoNumero}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/boleto/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/boleto/${nossoNumero}/pdf (src/hooks/useItauBank.ts:166)
`src/hooks/useItauBank.ts:166` calls `GET /api/itau/boleto/${nossoNumero}/pdf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/boleto/<p>/pdf` If this points at an external API, prefix it with `https://` so the …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/extrato (src/hooks/useItauBank.ts:126)
`src/hooks/useItauBank.ts:126` calls `GET /api/itau/extrato` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/extrato` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/pix/recebidos (src/hooks/useItauBank.ts:139)
`src/hooks/useItauBank.ts:139` calls `GET /api/itau/pix/recebidos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/pix/recebidos` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/saldo (src/hooks/useItauBank.ts:121)
`src/hooks/useItauBank.ts:121` calls `GET /api/itau/saldo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/saldo` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/itau/status (src/hooks/useItauBank.ts:101)
`src/hooks/useItauBank.ts:101` calls `GET /api/itau/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/status` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/config/llm (src/components/DevelopmentConsole/LlmSettingsTab.tsx:221)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:221` calls `POST /api/admin/config/llm` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm` If this points at an external API, prefix it with `https…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/config/llm/modules (src/components/DevelopmentConsole/LlmSettingsTab.tsx:239)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:239` calls `POST /api/admin/config/llm/modules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/modules` If this points at an external API, prefi…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/config/llm/playground (src/components/DevelopmentConsole/LlmSettingsTab.tsx:305)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:305` calls `POST /api/admin/config/llm/playground` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/playground` If this points at an external API,…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/config/llm/prompts (src/components/DevelopmentConsole/LlmSettingsTab.tsx:252)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:252` calls `POST /api/admin/config/llm/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/prompts` If this points at an external API, prefi…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/config/llm/test (src/components/DevelopmentConsole/LlmSettingsTab.tsx:275)
`src/components/DevelopmentConsole/LlmSettingsTab.tsx:275` calls `POST /api/admin/config/llm/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/config/llm/test` If this points at an external API, prefix it w…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/restart (src/components/AdminApp.tsx:59)
`src/components/AdminApp.tsx:59` calls `POST /api/admin/restart` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/restart` 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/banking/analyze/anomalies (src/components/Banking/BankingInsightsPanel.tsx:64)
`src/components/Banking/BankingInsightsPanel.tsx:64` calls `POST /api/banking/analyze/anomalies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/banking/analyze/anomalies` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/banking/import/auto (src/components/Banking/BankStatementImport.tsx:79)
`src/components/Banking/BankStatementImport.tsx:79` calls `POST /api/banking/import/auto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/banking/import/auto` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/banking/insights/cash-flow (src/components/Banking/BankingInsightsPanel.tsx:48)
`src/components/Banking/BankingInsightsPanel.tsx:48` calls `POST /api/banking/insights/cash-flow` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/banking/insights/cash-flow` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/send (src/components/Banking/SendDocumentModal.tsx:62)
`src/components/Banking/SendDocumentModal.tsx:62` calls `POST /api/documents/send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/documents/send` 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/github/issues (src/services/githubService.ts:85)
`src/services/githubService.ts:85` calls `POST /api/github/issues` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/github/issues` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/github/issues/${issueNumber}/labels (src/services/githubService.ts:73)
`src/services/githubService.ts:73` calls `POST /api/github/issues/${issueNumber}/labels` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/github/issues/<p>/labels` If this points at an external API, prefix it with `ht…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/github/issues/${issueNumber}/state (src/services/githubService.ts:61)
`src/services/githubService.ts:61` calls `POST /api/github/issues/${issueNumber}/state` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/github/issues/<p>/state` If this points at an external API, prefix it with `http…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/itau/boleto (src/hooks/useItauBank.ts:147)
`src/hooks/useItauBank.ts:147` calls `POST /api/itau/boleto` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/boleto` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/itau/boleto/${nossoNumero}/baixar (src/hooks/useItauBank.ts:173)
`src/hooks/useItauBank.ts:173` calls `POST /api/itau/boleto/${nossoNumero}/baixar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/boleto/<p>/baixar` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/itau/certificates (src/hooks/useItauBank.ts:113)
`src/hooks/useItauBank.ts:113` calls `POST /api/itau/certificates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/certificates` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/itau/pix/cobranca (src/hooks/useItauBank.ts:134)
`src/hooks/useItauBank.ts:134` calls `POST /api/itau/pix/cobranca` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/pix/cobranca` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/itau/test (src/hooks/useItauBank.ts:106)
`src/hooks/useItauBank.ts:106` calls `POST /api/itau/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/itau/test` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://google.serper.dev/search (backend/src/services/scraperService.ts:23)
`backend/src/services/scraperService.ts:23` calls `POST https://google.serper.dev/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/google.serper.dev/search` If this points at an external API, prefix it …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/dashboard/artifacts/financial (src/services/dashboardArtifacts.ts:25)
`src/services/dashboardArtifacts.ts:25` calls `PUT /api/dashboard/artifacts/financial` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/dashboard/artifacts/financial` If this points at an external API, prefix it with …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/dashboard/artifacts/forecast (src/services/dashboardArtifacts.ts:34)
`src/services/dashboardArtifacts.ts:34` calls `PUT /api/dashboard/artifacts/forecast` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/dashboard/artifacts/forecast` If this points at an external API, prefix it with `h…
Dangling fetchAxios
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/Email/EmailReadingPane.tsx:233
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 — src/components/HR/modals/ExpenseDetailModal.tsx:299
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 — src/components/InterventionList.tsx:360
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 — src/components/InvoiceList.tsx:753
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 — src/components/ProposalList.tsx:789
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 — src/components/SupplierInvoiceList.tsx:640
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 — src/components/SupplierProposalList.tsx:660
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 — src/components/TaskDetail.tsx:343
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 — src/components/TicketList.tsx:328
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 — src/components/VenueList.tsx:275
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 — src/utils/sanitizeHtml.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 quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/components/Banking/BankingInsightsPanel.tsx:64
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 — src/components/SchedulerAdmin.tsx:199
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 — src/hooks/useNotifications.ts:179
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 — src/services/api/core.ts:555
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. 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 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 quality Integrity conf 1.00 76 occurrences Frontend route `/customers/new` has no Link/navigate to it — src/components/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
76 occurrences
repo-level (76 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/Email/EmailReadingPane.tsx:233
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/Email/EmailReadingPane.tsx:233 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/HR/modals/ExpenseDetailModal.tsx:299
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/HR/modals/ExpenseDetailModal.tsx:299 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/InterventionList.tsx:360
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/InterventionList.tsx:360 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/InvoiceList.tsx:753
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/InvoiceList.tsx:753 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ProposalList.tsx:789
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/ProposalList.tsx:789 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/SupplierInvoiceList.tsx:640
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/SupplierInvoiceList.tsx:640 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/SupplierProposalList.tsx:660
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/SupplierProposalList.tsx:660 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/TaskDetail.tsx:343
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/TaskDetail.tsx:343 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/TicketList.tsx:328
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/TicketList.tsx:328 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/VenueList.tsx:275
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/VenueList.tsx:275 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/utils/sanitizeHtml.tsx:42
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/utils/sanitizeHtml.tsx:42 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/components/common/RichTextEditor.tsx:21
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/components/common/RichTextEditor.tsx:21 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/components/ui/RichTextEditor.tsx:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/components/ui/RichTextEditor.tsx:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/routes/githubRoutes.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/routes/githubRoutes.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/scripts/check-dolibarr-cookie.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/scripts/check-dolibarr-cookie.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/services/agentTools.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/services/agentTools.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/services/taskPlannerService.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/services/taskPlannerService.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/services/taskRunnerService.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/services/taskRunnerService.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/services/tunnelService.ts:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/services/tunnelService.ts:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/src/utils/processTree.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/src/utils/processTree.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in vite.config.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
vite.config.ts:2 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 302 placeholder/mock markers across 106 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 Integrity conf 1.00 29 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `APPROVAL_HISTORY_RETENTION_DAYS`, `APPROVAL_PENDING_TTL_HOURS`, `APP_VERSION`, `CI`, `CLOUDFLARE_TUNNEL_ENABLED`, `CLOUDFLARE_TUNNEL_TARGET`, `DEEPLINK_TOKEN_SECRET`, `DEV` + 21 more. Add them (with a placeholder/comment) to .env.example so onboar…
config drift
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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 636 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 src/components/ActivityReportModal.tsx:136
Found a known-risky pattern (document_write). Review and replace if possible.
src/components/ActivityReportModal.tsx:136 Document write
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 `eventscale_snapshots_v1` in src/pages/Simulator/components/modals/SavedSimulationsModal.tsx:21
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 `t2a_v2` in backend/src/__tests__/services/minimaxService.test.ts:22
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 `t2a_v2` in backend/src/services/minimaxService.ts:52
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 — backend/scripts/test-integration.ts:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/scripts/test_partnerships.ts:31
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/check-connection.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/check-connections.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/check-dolibarr-cookie.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/check-user-permissions.ts:20
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/count-tasks-standard.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/count-tasks.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-admin-check.ts:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-auth.ts:7
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-dolibarr.ts:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-rights.ts:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-signature.ts:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-task-627.js:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-tasks-raw.js:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-tasks-raw.ts:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-user-fields.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/debug-whatsapp.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/investigate-permissions.ts: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 — backend/src/scripts/run-taskrunner-canary.ts:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-audio-send.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-client-stripping.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-custom-sync.ts:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-date-handling.ts:243
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-delta-sync.ts: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 — backend/src/scripts/test-dolibarr-proxy.ts:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-inter-api.ts:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-puppeteer.js:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-real-login.ts:20
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-voice-note-native.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-vuln.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-whatsapp-qr.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test-whatsapp.ts:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test_date_conversion.ts:28
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/test_events_mapping.ts:44
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/testEmailConnection.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/verify-session-rename.ts:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/verify-user-rights.ts:38
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/src/scripts/verify_params.ts:14
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 — scripts/comprehensive-ui-test.ts:35
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 — scripts/coolgroove-complete-test.ts:78
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 — scripts/diagnostics/analyze_api_gaps.js:6
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 — scripts/diagnostics/analyze_data_density.js:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/diagnostics/analyze_data_links.js:11
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 — scripts/explore-all-pages.ts:49
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 — scripts/import-mars-tasks.ts:202
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 — scripts/interactive-browser.ts:9
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 — scripts/migrate-chat-events.ts:97
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 — scripts/test-own-app.ts:9
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 — scripts/web-scraper.ts:9
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 — src/components/Finance/ReceiptWizard.tsx:55
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 — src/scripts/compare_tasks.ts:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/scripts/debug_tasks_placeholder.ts:27
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 — src/scripts/test_sync.js:9
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 — src/scripts/verify_permission_logic.js:82
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 — src/scripts/verify_permission_logic.ts:103
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 — src/services/backgroundSyncService.ts:123
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/ui-crawler.spec.ts:91
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 /profile/picture
`backend/src/routes/whatsappRoutes.ts` declares `DELETE /profile/picture` 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 /sessions/:sessionId
`backend/src/routes/whatsappRoutes.ts` declares `DELETE /sessions/:sessionId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/tunnel/url
`backend/src/server.ts` declares `GET /api/tunnel/url` 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 /boleto/:banco/:nossoNumero/preview
`backend/src/routes/documentRoutes.ts` declares `GET /boleto/:banco/:nossoNumero/preview` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /check-number/:number
`backend/src/routes/whatsappRoutes.ts` declares `GET /check-number/:number` 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 /conversations
`backend/src/routes/whatsappRoutes.ts` declares `GET /conversations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /messages/:chatId
`backend/src/routes/whatsappRoutes.ts` declares `GET /messages/:chatId` 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 /messages/:messageId/media
`backend/src/routes/whatsappRoutes.ts` declares `GET /messages/:messageId/media` 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: GET /profile
`backend/src/routes/whatsappRoutes.ts` declares `GET /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: GET /qrcode
`backend/src/routes/whatsappRoutes.ts` declares `GET /qrcode` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sessions
`backend/src/routes/whatsappRoutes.ts` declares `GET /sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /settings/chat/:chatId
`backend/src/routes/whatsappRoutes.ts` declares `GET /settings/chat/:chatId` 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 /settings/session/:sessionId
`backend/src/routes/whatsappRoutes.ts` declares `GET /settings/session/:sessionId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /store
`backend/src/routes/whatsappRoutes.ts` declares `GET /store` 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 /assign
`backend/src/routes/whatsappRoutes.ts` declares `POST /assign` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`backend/src/routes/authRoutes.ts` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /logout
`backend/src/routes/authRoutes.ts` declares `POST /logout` 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 /profile/name
`backend/src/routes/whatsappRoutes.ts` declares `POST /profile/name` 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 /profile/picture
`backend/src/routes/whatsappRoutes.ts` declares `POST /profile/picture` 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 /profile/presence
`backend/src/routes/whatsappRoutes.ts` declares `POST /profile/presence` 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 /profile/status
`backend/src/routes/whatsappRoutes.ts` declares `POST /profile/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /send
`backend/src/routes/whatsappRoutes.ts` declares `POST /send` 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 /send-file
`backend/src/routes/whatsappRoutes.ts` declares `POST /send-file` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /send-voice
`backend/src/routes/whatsappRoutes.ts` declares `POST /send-voice` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /send-voice-native
`backend/src/routes/whatsappRoutes.ts` declares `POST /send-voice-native` 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 /settings/chat
`backend/src/routes/whatsappRoutes.ts` declares `POST /settings/chat` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /settings/session
`backend/src/routes/whatsappRoutes.ts` declares `POST /settings/session` 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 /settings/user
`backend/src/routes/whatsappRoutes.ts` declares `POST /settings/user` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /start
`backend/src/routes/whatsappRoutes.ts` declares `POST /start` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhook
`backend/src/routes/whatsappRoutes.ts` declares `POST /webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/admin
`backend/src/server.ts` declares `USE /api/admin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/ai
`backend/src/server.ts` declares `USE /api/ai` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/approvals
`backend/src/server.ts` declares `USE /api/approvals` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/auth
`backend/src/server.ts` declares `USE /api/auth` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/banking
`backend/src/server.ts` declares `USE /api/banking` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/centrovibe
`backend/src/server.ts` declares `USE /api/centrovibe` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/dashboard
`backend/src/server.ts` declares `USE /api/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/documents
`backend/src/server.ts` declares `USE /api/documents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/dolibarr
`backend/src/server.ts` declares `USE /api/dolibarr` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/email
`backend/src/server.ts` declares `USE /api/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/github
`backend/src/server.ts` declares `USE /api/github` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/integration
`backend/src/server.ts` declares `USE /api/integration` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/inter
`backend/src/server.ts` declares `USE /api/inter` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/itau
`backend/src/server.ts` declares `USE /api/itau` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/notifications
`backend/src/server.ts` declares `USE /api/notifications` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/scheduler
`backend/src/server.ts` declares `USE /api/scheduler` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/tasks
`backend/src/server.ts` declares `USE /api/tasks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/ui-config
`backend/src/server.ts` declares `USE /api/ui-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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/webhook
`backend/src/server.ts` declares `USE /api/webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/whatsapp
`backend/src/server.ts` declares `USE /api/whatsapp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/src/services/agentTools.ts (1866 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/services/aiService.ts (1531 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/services/taskRunnerService.ts (2581 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/src/types/dolibarr.actions.d.ts (18144 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/BankAccountList.tsx (866 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/CustomerList.tsx (1080 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/DevelopmentConsole/LlmSettingsTab.tsx (988 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/InvoiceList.tsx (1126 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/Issues/IssuesPage.tsx (907 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/ProposalList.tsx (1063 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/SchedulerAdmin.tsx (1645 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/SupplierInvoiceList.tsx (1013 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/SupplierProposalList.tsx (909 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/Tasks/UserTaskDashboard.tsx (1076 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/TasksBoard/TasksBoard.tsx (892 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/types/dolibarr.actions.d.ts (18144 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/7a395cb8-e454-48d5-8a8c-e2aabeca639a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7a395cb8-e454-48d5-8a8c-e2aabeca639a/

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.