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

Azaz3lfall/traccarFull

https://github.com/Azaz3lfall/traccarFull · scanned 2026-06-17 01:21 UTC (1 month, 2 weeks ago)

312 raw signals (0 security + 312 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -14.9 (diff) · 243 actionable findings from 1 signal source. 69 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
61.8
/100
Security checks
62
0 findings
System graph
62
88.9% cov · 243 findings
Critical
7
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 7 High 55 Medium 53 Low 120 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 243 Crowd 0 Layer: Frontend 46 Network 1 Security 20 Cicd 1 Quality 72 Api 103
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 61.8/100 with 88.9% coverage. It contains 3230 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 312 findings — concentrated in quality (139), api (103), frontend (46). Risk profile is high: 9 critical, 55 high, 120 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 235 of 243 actionable findings. 312 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 src/addons/gestao_backend/schedulers/commandEventMonitor.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/addons/gestao_backend/schedulers/commandEventMonitor.js:39
critical System graph security Secrets conf 1.00 Possible secret in src/addons/gestao_backend/schedulers/j16DoorMonitor.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/addons/gestao_backend/schedulers/j16DoorMonitor.js:51
critical System graph security Secrets conf 1.00 Possible secret in src/addons/reseller/resellersServer.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/addons/reseller/resellersServer.mjs:134
critical System graph security Secrets conf 1.00 Possible secret in src/addons/tags/tag.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/addons/tags/tag.js:3
critical System graph security Secrets conf 1.00 Possible secret in src/addons/tags/tags.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
src/addons/tags/tags.mjs:7
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/other/gestao/components/DriverCompleteModal.jsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 134, 197
src/other/gestao/components/DriverCompleteModal.jsx:134, 197 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/other/gestao/components/DriverCreateModal.jsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 125, 194
src/other/gestao/components/DriverCreateModal.jsx:125, 194 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/calendars/${calendarId} (src/components/FloatingCalendarsPopover.jsx:278)
`src/components/FloatingCalendarsPopover.jsx:278` calls `DELETE /api/calendars/${calendarId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/calendars/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/groups/${groupId} (src/components/FloatingGroupsPopover.jsx:218)
`src/components/FloatingGroupsPopover.jsx:218` calls `DELETE /api/groups/${groupId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/groups/<p>` 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: DELETE /api/session (src/common/components/BottomMenu.jsx:75)
`src/common/components/BottomMenu.jsx:75` calls `DELETE /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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: DELETE /api/session (src/main/MainPage.jsx:432)
`src/main/MainPage.jsx:432` calls `DELETE /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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: DELETE /api/session (src/other/gestao/utils/authManager.js:260)
`src/other/gestao/utils/authManager.js:260` calls `DELETE /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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: DELETE /api/session (src/settings/ClientFinancialPage.jsx:98)
`src/settings/ClientFinancialPage.jsx:98` calls `DELETE /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/calendars (src/components/FloatingCalendarsPopover.jsx:161)
`src/components/FloatingCalendarsPopover.jsx:161` calls `GET /api/calendars` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/calendars` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/commands/types (src/settings/components/BaseCommandView.jsx:60)
`src/settings/components/BaseCommandView.jsx:60` calls `GET /api/commands/types` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/commands/types` 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 /api/devices/${device.id} (src/components/FloatingStatusCard.jsx:3798)
`src/components/FloatingStatusCard.jsx:3798` calls `GET /api/devices/${device.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/devices/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/devices/${device.id} (src/components/FloatingStatusCard.jsx:3919)
`src/components/FloatingStatusCard.jsx:3919` calls `GET /api/devices/${device.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/devices/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/drivers (src/components/FloatingDriversPopover.jsx:64)
`src/components/FloatingDriversPopover.jsx:64` calls `GET /api/drivers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/drivers` 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/events/${eventId} (src/SocketController.jsx:215)
`src/SocketController.jsx:215` calls `GET /api/events/${eventId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/events/<p>` 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/groups (src/components/FloatingGroupsPopover.jsx:95)
`src/components/FloatingGroupsPopover.jsx:95` calls `GET /api/groups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/groups` 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/list-files (src/components/ResellersPage.jsx:12)
`src/components/ResellersPage.jsx:12` calls `GET /api/list-files` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/list-files` 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/positions (public/j16-door-status.js:347)
`public/j16-door-status.js:347` calls `GET /api/positions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/positions` 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/positions (src/SocketController.jsx:154)
`src/SocketController.jsx:154` calls `GET /api/positions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/positions` 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/positions?id=${position.id} (src/components/FloatingStatusCard.jsx:3350)
`src/components/FloatingStatusCard.jsx:3350` calls `GET /api/positions?id=${position.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/positions` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/server (src/components/UserManagementPopover.jsx:519)
`src/components/UserManagementPopover.jsx:519` calls `GET /api/server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server` 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/server (src/main/hooks/useServerData.js:11)
`src/main/hooks/useServerData.js:11` calls `GET /api/server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server` 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/server (src/other/gestao/utils/authManager.js:18)
`src/other/gestao/utils/authManager.js:18` calls `GET /api/server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server` 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/server (src/other/gestao/utils/authManager.js:45)
`src/other/gestao/utils/authManager.js:45` calls `GET /api/server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server` 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/server (src/ServerProvider.jsx:22)
`src/ServerProvider.jsx:22` calls `GET /api/server` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server` 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/session (src/App.jsx:53)
`src/App.jsx:53` calls `GET /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session (src/other/gestao/utils/authDiagnostic.js:16)
`src/other/gestao/utils/authDiagnostic.js:16` calls `GET /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session (src/other/gestao/utils/testAuth.js:7)
`src/other/gestao/utils/testAuth.js:7` calls `GET /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session?token=${encodeURIComponent(token)} (src/Navigation.jsx:106)
`src/Navigation.jsx:106` calls `GET /api/session?token=${encodeURIComponent(token)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/vehicles/available-devices (src/other/os/utils/api.js:29)
`src/other/os/utils/api.js:29` calls `GET /api/vehicles/available-devices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/vehicles/available-devices` If this points at an external API, prefix it with `https://` so t…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/vehicles/linked-devices (src/other/os/utils/api.js:31)
`src/other/os/utils/api.js:31` calls `GET /api/vehicles/linked-devices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/vehicles/linked-devices` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /auth/user (src/other/gestao/utils/testApi.js:10)
`src/other/gestao/utils/testApi.js:10` calls `GET /auth/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/user` 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 http://localhost:8082/api/devices?all=true (src/addons/gestao_backend/schedulers/j16DoorMonitor.js:85)
`src/addons/gestao_backend/schedulers/j16DoorMonitor.js:85` calls `GET http://localhost:8082/api/devices?all=true` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:8082/api/devices` If this points at a…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/calendars (src/components/FloatingCalendarsPopover.jsx:226)
`src/components/FloatingCalendarsPopover.jsx:226` calls `POST /api/calendars` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/calendars` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/drivers (src/components/FloatingDriversPopover.jsx:118)
`src/components/FloatingDriversPopover.jsx:118` calls `POST /api/drivers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/drivers` 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/groups (src/components/FloatingGroupsPopover.jsx:160)
`src/components/FloatingGroupsPopover.jsx:160` calls `POST /api/groups` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/groups` 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/server/reboot (src/main/hooks/usePreferencesDrawer.js:58)
`src/main/hooks/usePreferencesDrawer.js:58` calls `POST /api/server/reboot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server/reboot` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/server/reboot (src/settings/PreferencesPage.jsx:85)
`src/settings/PreferencesPage.jsx:85` calls `POST /api/server/reboot` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/server/reboot` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/session (src/components/fleet/FleetVehicleCard.jsx:457)
`src/components/fleet/FleetVehicleCard.jsx:457` calls `POST /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session (src/login/LoginPage.jsx:162)
`src/login/LoginPage.jsx:162` calls `POST /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session (src/other/gestao/utils/authDiagnostic.js:127)
`src/other/gestao/utils/authDiagnostic.js:127` calls `POST /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session/token (src/common/components/NativeInterface.js:23)
`src/common/components/NativeInterface.js:23` calls `POST /api/session/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session/token` 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: POST /api/vehicles/upload (src/components/management/VehicleRegisterModal.jsx:182)
`src/components/management/VehicleRegisterModal.jsx:182` calls `POST /api/vehicles/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/vehicles/upload` 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/vehicles/upload (src/other/os/components/OSDashboard.jsx:349)
`src/other/os/components/OSDashboard.jsx:349` calls `POST /api/vehicles/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/vehicles/upload` 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: POST /api/vehicles/upload (src/settings/components/vehicles/VehicleFormDialog.jsx:188)
`src/settings/components/vehicles/VehicleFormDialog.jsx:188` calls `POST /api/vehicles/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/vehicles/upload` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:8082/api/session (src/addons/gestao_backend/schedulers/j16DoorMonitor.js:70)
`src/addons/gestao_backend/schedulers/j16DoorMonitor.js:70` calls `POST http://localhost:8082/api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/http:/localhost:8082/api/session` If this points at an extern…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudinary.com/v1_1/${cloudName}/image/destroy (src/utils/cloudinary.js:167)
`src/utils/cloudinary.js:167` calls `POST https://api.cloudinary.com/v1_1/${cloudName}/image/destroy` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudinary.com/v1_1/<p>/image/destroy` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.cloudinary.com/v1_1/${cloudName}/image/upload (src/utils/cloudinary.js:94)
`src/utils/cloudinary.js:94` calls `POST https://api.cloudinary.com/v1_1/${cloudName}/image/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudinary.com/v1_1/<p>/image/upload` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://fcm.googleapis.com/v1/projects/${PROJECT_ID}/messages:send (src/addons/gestao_backend/schedulers/doorPush.js:73)
`src/addons/gestao_backend/schedulers/doorPush.js:73` calls `POST https://fcm.googleapis.com/v1/projects/${PROJECT_ID}/messages:send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/fcm.googleapis.com/v1/proje…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (src/addons/gestao_backend/schedulers/doorPush.js:58)
`src/addons/gestao_backend/schedulers/doorPush.js:58` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/calendars/${calendarData.id} (src/components/FloatingCalendarsPopover.jsx:252)
`src/components/FloatingCalendarsPopover.jsx:252` calls `PUT /api/calendars/${calendarData.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/calendars/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/devices/${device.id} (src/components/FloatingStatusCard.jsx:3782)
`src/components/FloatingStatusCard.jsx:3782` calls `PUT /api/devices/${device.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/devices/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/devices/${device.id} (src/components/FloatingStatusCard.jsx:3901)
`src/components/FloatingStatusCard.jsx:3901` calls `PUT /api/devices/${device.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/devices/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/devices/${device.id} (src/components/FloatingStatusCard.jsx:4059)
`src/components/FloatingStatusCard.jsx:4059` calls `PUT /api/devices/${device.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/devices/<p>` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/groups/${groupData.id} (src/components/FloatingGroupsPopover.jsx:189)
`src/components/FloatingGroupsPopover.jsx:189` calls `PUT /api/groups/${groupData.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/groups/<p>` 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: PUT /api/users/${user.id} (src/common/components/BottomMenu.jsx:66)
`src/common/components/BottomMenu.jsx:66` calls `PUT /api/users/${user.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/users/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/addons/reseller/resellersServer.mjs:2235
Found a known-risky pattern (exec_used). Review and replace if possible.
src/addons/reseller/resellersServer.mjs:2235 Exec used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/components/FloatingDataAnalyticsPopover.jsx:1744
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/components/FloatingDataAnalyticsPopover.jsx:1744 New function used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/ErrorBoundary.jsx:22
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 — public/j16-door-status.js:336
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/addons/jtt-server/jtt-server.mjs:2283
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/addons/tags/nanotag.mjs:107
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/addons/telecom/scripts/syncDevicesToChips.js:33
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/App.jsx:53
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/common/components/BottomMenu.jsx:66
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/common/util/fetchOrThrow.js:2
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/common/util/formatter.js:189
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/FloatingCalendarsPopover.jsx:161
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/FloatingDataAnalyticsPopover.jsx:2783
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/FloatingDevicesPopover.jsx:439
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/FloatingDriversPopover.jsx: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/FloatingGeofencesPopover.jsx:1235
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/FloatingGroupsPopover.jsx:95
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/FloatingResellersPopover.jsx:265
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/FloatingStatusCard.jsx:458
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/config/resellersConfig.js:40
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/main/hooks/usePreferencesDrawer.js:58
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/main/hooks/useServerData.js:11
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/main/MainPage.jsx:316
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/map/main/PoiMap.js:20
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/map/MapRoutePath.js:227
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/Navigation.jsx:106
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/other/gestao/GestaoPageModular.jsx:336
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/other/gestao/hooks/useDrivers.js:216
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/other/gestao/hooks/useExtraCosts.js:35
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/other/gestao/hooks/useGestaoData.js:79
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/other/gestao/hooks/useMaintenances.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 — src/other/gestao/hooks/useRefuels.js:113
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/other/gestao/utils/authManager.js:172
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/settings/PreferencesPage.jsx:85
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/SocketController.jsx:154
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/store/fleet.js:29
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/UpdateController.jsx:28
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/utils/cloudinary.js:94
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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 68 occurrences Frontend route `/briefing` has no Link/navigate to it — src/Navigation.jsx
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.
68 occurrences
repo-level (68 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/addons/dataAnalytics/dataAnalyticsServer.mjs:50
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/addons/dataAnalytics/dataAnalyticsServer.mjs:50 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/addons/rbac/rbacServer.mjs:28
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/addons/rbac/rbacServer.mjs:28 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/addons/reseller/resellersServer.mjs:671
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/addons/reseller/resellersServer.mjs:671 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/addons/traccar_wrapper/core/core.js:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/addons/traccar_wrapper/core/core.js:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/ErrorBoundary.jsx:22
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/ErrorBoundary.jsx:22 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/j16-door-status.js:62
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/j16-door-status.js:62 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/components/FloatingDataAnalyticsPopover.jsx:852
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/components/FloatingDataAnalyticsPopover.jsx:852 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/SharedDevicePage.jsx:39
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/SharedDevicePage.jsx:39 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in src/common/components/NativeInterface.js:66
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
src/common/components/NativeInterface.js:66 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/addons/jtt-server/jtt-server.mjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/addons/jtt-server/jtt-server.mjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/addons/reseller/resellersServer.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/addons/reseller/resellersServer.mjs:11 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 143 placeholder/mock markers across 64 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 91 in use
Port 91 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/generate-dev-cert-with-ip.sh Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 445 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: tests, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 889 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy___.yml:14 CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: src/addons/dataAnalytics/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.
src/addons/dataAnalytics/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: src/addons/jtt-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.
src/addons/jtt-server/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: src/addons/rbac/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.
src/addons/rbac/package.json LockfileReproducibilityGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/sync_full_system.js:23
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/addons/gestao_backend/schedulers/commandEventMonitor.js:109
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/addons/gestao_backend/schedulers/commandScheduler.js:151
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/addons/gestao_backend/schedulers/doorPush.js:156
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/addons/gestao_backend/schedulers/j16DoorMonitor.js:76
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/addons/gestao_backend/schedulers/routeBlockMonitor.js:207
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/addons/gestao_backend/server.js:83
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/addons/tags/tag.js: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 — src/addons/telecom/scripts/syncDevicesToChips.js:75
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/addons/telecom/scripts/verifyVoxterCredentials.js: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 — src/addons/traccar_wrapper/core/core.js:47
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/addons/traccar_wrapper/db/index.js:46
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/addons/traccar_wrapper/db/migrate_consolidate_users.js:36
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/common/hooks/useFriendlyNotifications.js:53
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/FloatingDeviceList.jsx:2525
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/FloatingDevicesPopover.jsx:292
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/FloatingReportsPopover.jsx:1145
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/FloatingResellersPopover.jsx:278
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/FloatingStatusCard.jsx:368
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/ModernDeviceList.jsx:172
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/ModernMainPage.jsx:220
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/middleware/authMiddleware.js: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 — src/other/gestao/components/AuthDiagnostic.jsx:46
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/other/gestao/components/AuthStatusIndicator.jsx: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 — src/other/gestao/components/DebugTab.jsx:76
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/other/gestao/components/DriversTab.jsx:142
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/other/gestao/components/ExtraCostsTab.jsx:76
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/other/gestao/components/MaintenancesTab.jsx:74
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/other/gestao/components/RefuelingReportsTab.jsx:50
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/other/gestao/components/RefuelsTab.jsx:74
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/other/gestao/components/ReportsTab.jsx:96
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/other/gestao/GestaoPageModular.jsx:54
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/other/gestao/hooks/useGestaoData.js: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 — src/other/gestao/hooks/useRefuels.js:93
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/other/gestao/utils/authDiagnostic.js:3
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/other/gestao/utils/authManager.js: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 — src/other/gestao/utils/formatters.js: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 — src/other/gestao/utils/testApi.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 — src/other/gestao/utils/testAuth.js:3
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/routes/fleetRoutes.js:17
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/routes/gestaoRoutes.js:144
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/routes/traccarPermissions.js:42
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/routes/vehiclesRoutes.js:153
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/financialScheduler.js:117
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 /api/roles/:id
`src/addons/rbac/rbacServer.mjs` declares `DELETE /api/roles/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /gestao/maintenances/:id
`src/addons/gestao_backend/routes/maintenances.js` declares `DELETE /gestao/maintenances/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /work-orders/:id
`src/addons/os_backend/routes/os.routes.js` declares `DELETE /work-orders/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`src/addons/gestao_backend/server.js` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/reports/route
`src/addons/gestao_backend/routes/misc.js` declares `GET /api/reports/route` 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/roles
`src/addons/rbac/rbacServer.mjs` declares `GET /api/roles` 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 /app/motorista/profile
`src/addons/gestao_backend/routes/motorista.js` declares `GET /app/motorista/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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /app/motorista/trips
`src/addons/gestao_backend/routes/motorista.js` declares `GET /app/motorista/trips` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /clients
`src/other/os/utils/api.js` declares `GET /clients` 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 /gestao/abastecimentos/image/:filename
`src/addons/gestao_backend/routes/misc.js` declares `GET /gestao/abastecimentos/image/:filename` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/maintenances
`src/addons/gestao_backend/routes/maintenances.js` declares `GET /gestao/maintenances` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/consumo-medio
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/consumo-medio` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/custo-abastecimento-total
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/custo-abastecimento-total` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/custos-extras
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/custos-extras` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/custos-por-categoria
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/custos-por-categoria` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/custos-por-viagem
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/custos-por-viagem` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/relatorios/distancia-abastecimentos
`src/addons/gestao_backend/routes/reports.js` declares `GET /gestao/relatorios/distancia-abastecimentos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /gestao/uploads/:filename
`src/addons/gestao_backend/routes/misc.js` declares `GET /gestao/uploads/:filename` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /os-api/clients
`src/addons/os_backend/routes/index.js` declares `GET /os-api/clients` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /users
`src/other/os/utils/api.js` declares `GET /users` 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 /work-orders
`src/other/os/utils/api.js` declares `GET /work-orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /work-orders/:id
`src/addons/os_backend/routes/os.routes.js` declares `GET /work-orders/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /work-orders/by-plate/:plate
`src/addons/os_backend/routes/os.routes.js` declares `GET /work-orders/by-plate/:plate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /work-orders/:id
`src/addons/os_backend/routes/os.routes.js` declares `PATCH /work-orders/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /work-orders/:id/status
`src/addons/os_backend/routes/os.routes.js` declares `PATCH /work-orders/:id/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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/permissions
`src/addons/os_backend/services/traccar.service.js` declares `POST /api/permissions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/roles
`src/addons/rbac/rbacServer.mjs` declares `POST /api/roles` 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 /app/motorista/custos
`src/addons/gestao_backend/routes/motorista.js` declares `POST /app/motorista/custos` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /app/motorista/custos-avulsos
`src/addons/gestao_backend/routes/motorista.js` declares `POST /app/motorista/custos-avulsos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /app/motorista/refuelings
`src/addons/gestao_backend/routes/motorista.js` declares `POST /app/motorista/refuelings` 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: POST /app/motorista/upload
`src/addons/gestao_backend/routes/motorista.js` declares `POST /app/motorista/upload` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /checklist
`src/other/os/utils/api.js` declares `POST /checklist` 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 /gestao/maintenances
`src/addons/gestao_backend/routes/maintenances.js` declares `POST /gestao/maintenances` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /gestao/refuelings
`src/addons/gestao_backend/routes/refuelings.js` declares `POST /gestao/refuelings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /link-device
`src/addons/os_backend/routes/traccar.routes.js` declares `POST /link-device` 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
`src/addons/os_backend/routes/traccar.routes.js` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /toggle-technician
`src/other/os/utils/api.js` declares `POST /toggle-technician` 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 /users
`src/addons/os_backend/routes/traccar.routes.js` declares `POST /users` 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 /work-orders
`src/other/os/utils/api.js` declares `POST /work-orders` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /work-orders/:id/photos
`src/addons/os_backend/routes/os.routes.js` declares `POST /work-orders/:id/photos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /work-orders/:id/signature
`src/addons/os_backend/routes/os.routes.js` declares `POST /work-orders/:id/signature` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/roles/:id
`src/addons/rbac/rbacServer.mjs` declares `PUT /api/roles/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /app/motorista/trips/:id/finalizar
`src/addons/gestao_backend/routes/motorista.js` declares `PUT /app/motorista/trips/:id/finalizar` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /gestao/maintenances/:id
`src/addons/gestao_backend/routes/maintenances.js` declares `PUT /gestao/maintenances/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`src/addons/gestao_backend/server.js` declares `USE /api` 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 /gestao
`src/addons/gestao_backend/server.js` declares `USE /gestao` 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 /os-api
`src/addons/os_backend/routes/index.js` declares `USE /os-api` 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 /os-uploads
`src/addons/os_backend/routes/index.js` declares `USE /os-uploads` 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 /traccar-api
`src/addons/os_backend/routes/index.js` declares `USE /traccar-api` 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 /uploads
`src/addons/gestao_backend/server.js` declares `USE /uploads` 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: src/addons/jtt-server/jtt-server.mjs (2574 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/addons/reseller/resellersServer.mjs (4086 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/fleet/FleetVehicleCard.jsx (1385 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/FloatingCalendarsPopover.jsx (1724 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/FloatingComputedAttributesPopover.jsx (1207 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/FloatingDataAnalyticsPopover.jsx (4880 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/FloatingDeviceList.jsx (3724 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/FloatingDevicesPopover.jsx (2727 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/FloatingGeofencesPopover.jsx (3828 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/FloatingNotificationsPopover.jsx (1305 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/FloatingReportsPopover.jsx (3946 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/FloatingResellersPopover.jsx (5412 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/FloatingStatusCard.jsx (10831 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/UserManagementPopover.jsx (2832 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/main/MainPage.jsx (5017 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/other/HistoryPanel.jsx (1810 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/financialRoutes.js (1520 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/routes/vehiclesRoutes.js (1454 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/settings/components/VehicleDetailsModal.jsx (1836 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/settings/FinancialPage.jsx (1072 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/24ad530f-b999-46eb-91d1-802165c9f919/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/24ad530f-b999-46eb-91d1-802165c9f919/

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.