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.

soakal/VRSI-Wallboard

https://github.com/soakal/VRSI-Wallboard · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

122 raw signals (0 security + 122 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 8 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/`.
8 matching findings on this repo
  • info Commented-code block (5 lines) in client/src/App.tsx:128
  • info Commented-code block (6 lines) in client/src/components/AgendaRail.tsx:48
  • info Commented-code block (6 lines) in client/src/hooks/useEvents.ts:23
  • info Commented-code block (5 lines) in server/src/utils/icsGenerator.ts:12
  • info Commented-code block (5 lines) in server/src/routes/update.ts:120
  • info Commented-code block (6 lines) in server/src/routes/board.ts:28
  • info Commented-code block (8 lines) in server/src/services/boardService.ts:27
  • info Commented-code block (6 lines) in e2e/reset-data.cjs:1
View all commented-out code findings →
Config drift 5 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.
5 matching findings on this repo
  • medium `fetch()` without try/.catch or AbortSignal — client/src/api/configApi.ts:5
  • high Dangling fetch: GET /api/board/config (client/src/api/boardApi.ts:19)
  • high Dangling fetch: POST /api/board/config (client/src/api/boardApi.ts:24)
  • high Dangling fetch: GET /api/config/geocode?q=${encodeURIComponent(query)} (client/…
  • low Unused endpoint: USE /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/bb5b2a2d-f17f-4243-bc92-08695b7e280e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bb5b2a2d-f17f-4243-bc92-08695b7e280e/

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.