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.

selimmujdeci/Car-launcher-pro

https://github.com/selimmujdeci/Car-launcher-pro · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

182 raw signals (0 security + 182 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 169 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 47 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 169 Crowd 0 Layer: Api 1 Frontend 57 Security 9 Cicd 2 Quality 100

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `matchesLegacy` in src/platform/wakeWordService.ts:…

View all legacy markers findings →

Commented-out code 38 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in vite.config.ts:10
info Commented-code block (7 lines) in website/supabase/functions/push-notify/index.…
info Commented-code block (5 lines) in website/src/app/api/vehicle/update/route.ts:67
info Commented-code block (5 lines) in website/src/app/api/vehicles/route.ts:29
info Commented-code block (6 lines) in supabase/functions/push-notify/index.ts:127
info Commented-code block (8 lines) in src/platform/youtubeService.ts:71
info Commented-code block (5 lines) in src/platform/commandParser.ts:211
info Commented-code block (5 lines) in src/platform/mapSourceManager.ts:54
info Commented-code block (5 lines) in src/platform/appDiscovery.ts:103
info Commented-code block (5 lines) in src/platform/musicCommandParser.ts:141
info Commented-code block (7 lines) in src/platform/thermalWatchdog.ts:479
info Commented-code block (7 lines) in src/platform/vehicleIdentityService.ts:363

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in vite.config.ts:10

View all config drift findings →

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/fe33e7cc-1b07-4b8f-8b90-82aa73588f3a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fe33e7cc-1b07-4b8f-8b90-82aa73588f3a/

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.