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
95 of your 660 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.57s · analysis 21.15s · 9.8 MB · GitHub API rate-limit (preflight)

clawvisor/clawvisor

https://github.com/clawvisor/clawvisor · scanned 2026-06-05 17:43 UTC (4 days, 21 hours ago) · 10 languages

626 raw signals (386 security + 240 graph) 9th percentile · Go · large (100-500K LoC) System graph score 65 (lower by 4)

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

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 216 actionable findings from 2 signal sources. 290 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
57.1
/100
Security checks
49
134 findings
System graph
65
100.0% cov · 82 findings
Critical
9
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 3.0 0.25 0.75
testing_score 80.0 0.20 16.00
documentation_score 100.0 0.15 15.00
practices_score 77.0 0.15 11.55
code_quality 41.4 0.10 4.14
Overall 1.00 60.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 9 High 83 Medium 25 Low 54 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 134 System graph 82 Crowd 0 Layer: Software 90 Cicd 14 Security 18 Quality 69 Api 1 Frontend 9 Network 2 Hardware 13

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 internal/clawvisorcli/shim/clawvisor-proxy-sh…
  • info Commented-code block (5 lines) in web/vite.config.ts:19
  • info Commented-code block (5 lines) in web/src/api/client.ts:217
  • info Commented-code block (6 lines) in web/src/components/TaskCard.tsx:139
  • info Commented-code block (5 lines) in web/src/pages/Agents.tsx:580
  • info Commented-code block (14 lines) in web/src/pages/Overview.tsx:345
  • info Commented-code block (7 lines) in web/src/pages/Settings.tsx:365
  • info Commented-code block (7 lines) in web/src/hooks/useAuth.tsx:137
View all commented-out code findings →
Config drift 4 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.
4 matching findings on this repo
  • low File has no detected symbols: web/vite.config.ts
  • low File has no detected symbols: web/tailwind.config.ts
  • low File has no detected symbols: web/postcss.config.js
  • info Commented-code block (5 lines) in web/vite.config.ts:19
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/32c90083-0b1f-4275-ac0e-ee264df3298f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/32c90083-0b1f-4275-ac0e-ee264df3298f/

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.