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

Scan timing: clone 3.03s · analysis 29.95s · 5.0 MB · GitHub preflight 437ms

xbrxr03/clawos

https://github.com/xbrxr03/clawos · scanned 2026-06-05 18:23 UTC (4 days, 19 hours ago) · 10 languages

787 raw signals (303 security + 484 graph) 48th percentile · Python · medium (20-100K LoC) System graph score 76 (lower by 14)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 21.1 0.25 5.28
testing_score 78.0 0.20 15.60
documentation_score 93.7 0.15 14.05
practices_score 86.0 0.15 12.90
code_quality 49.0 0.10 4.90
Overall 1.00 61.7
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.

Duplicates & near-duplicates 2 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
2 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places
View all duplicates & near-duplicates findings →
Legacy markers 10 findings
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.
10 matching findings on this repo
  • low Archive or legacy directory is mixed into the active repository root archive:1
  • high FastAPI POST `api_submit_task` without auth dependency — archive/legacy/dashboa… archive/legacy/dashboard-backend/service.py:185
  • high FastAPI POST `api_approve` without auth dependency — archive/legacy/dashboard-b… archive/legacy/dashboard-backend/service.py:242
  • high FastAPI POST `api_deny` without auth dependency — archive/legacy/dashboard-back… archive/legacy/dashboard-backend/service.py:247
  • high FastAPI POST `api_pull_model` without auth dependency — archive/legacy/dashboar… archive/legacy/dashboard-backend/service.py:282
  • high FastAPI DELETE `api_delete_model` without auth dependency — archive/legacy/dash… archive/legacy/dashboard-backend/service.py:289
  • high FastAPI POST `api_delegate` without auth dependency — archive/legacy/dashboard-… archive/legacy/dashboard-backend/service.py:568
  • high FastAPI POST `api_agent_reset` without auth dependency — archive/legacy/dashboa… archive/legacy/dashboard-backend/service.py:612
  • high FastAPI POST `api_nexus_chat` without auth dependency — archive/legacy/dashboar… archive/legacy/dashboard-backend/service.py:624
  • high FastAPI POST `api_workflow_run` without auth dependency — archive/legacy/dashbo… archive/legacy/dashboard-backend/service.py:662
View all legacy markers findings →
Config drift 6 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.
6 matching findings on this repo
  • low File has no detected symbols: dashboard/frontend/vite.config.js
  • high FastAPI POST `openclaw_configure` without auth dependency — services/setupd/ser… services/setupd/service.py:1266
  • low Unused endpoint: GET /api/voice/elevenlabs-config
  • low Unused endpoint: POST /api/voice/elevenlabs-config
  • low Unused endpoint: GET /api/jarvis/config
  • low Unused endpoint: POST /api/jarvis/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/c909edc4-e5b0-4649-b779-d5b64f392b1d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c909edc4-e5b0-4649-b779-d5b64f392b1d/

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.