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.

vibedeckx/vibedeckx

https://github.com/vibedeckx/vibedeckx · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

145 raw signals (6 security + 139 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 141 actionable findings from 2 signal sources. 6 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 · 136 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 2 Medium 30 Low 60 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 136 Crowd 0 Layer: Quality 53 Security 13 Frontend 59 Cicd 4 Api 12

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.

Commented-out code 24 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 (5 lines) in apps/vibedeckx-ui/components/agent/agent-conv…
info Commented-code block (5 lines) in apps/vibedeckx-ui/components/agent/session-hi…
info Commented-code block (6 lines) in apps/vibedeckx-ui/components/files/file-previ…
info Commented-code block (7 lines) in apps/vibedeckx-ui/components/executor/executo…
info Commented-code block (5 lines) in apps/vibedeckx-ui/components/executor/executo…
info Commented-code block (7 lines) in apps/vibedeckx-ui/app/page.tsx:119
info Commented-code block (5 lines) in apps/vibedeckx-ui/lib/api.ts:203
info Commented-code block (6 lines) in apps/vibedeckx-ui/lib/workspace-status.test.t…
info Commented-code block (5 lines) in apps/vibedeckx-ui/hooks/use-worktrees.ts:17
info Commented-code block (5 lines) in apps/vibedeckx-ui/hooks/use-marker-keyboard-n…
info Commented-code block (6 lines) in apps/vibedeckx-ui/hooks/use-agent-session.ts:…
info Commented-code block (5 lines) in apps/vibedeckx-ui/hooks/use-branch-activity.t…

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
low Unused endpoint: GET /api/config

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/567c8ce0-98ba-4129-b51f-93928f05191c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/567c8ce0-98ba-4129-b51f-93928f05191c/

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.