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: severity: info × 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 8 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.

info System graph quality Integrity conf 1.00 Commented-code block (12 lines) in src/other/gestao/GestaoPageModular.jsx:112
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (5 lines) in src/addons/jtt-server/jtt-server.mjs:237
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (5 lines) in src/addons/reseller/resellersServer.mjs:2524
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (5 lines) in src/components/FloatingStatusCard.jsx:3494
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (8 lines) in src/common/util/formatter.js:106
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (8 lines) in src/components/FloatingDataAnalyticsPopover.jsx:1735
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph quality Integrity conf 1.00 Commented-code block (8 lines) in src/SocketController.jsx:86
A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.
commented codeDead code
info System graph frontend Frontend quality conf 1.00 TODO/FIXME marker in shipping code — src/other/gestao/components/ExtraCostsTab.jsx:423
Track in /reviews or /issues, not as a code comment that rots. Why: Drift control — shouldn't be the same as Quality TODO scanner. Rule id: fq.todo-marker
Fq todo marker
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.