trycua/cua

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.

197 of your 323 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 153.68s for a 164.5 MB repo slow.
Repobility's analysis ran in 9.71s after the clone landed.

https://github.com/trycua/cua.git · scanned 2026-05-24 01:23 UTC (2 weeks, 6 days ago) · 10 languages

1475 raw signals (319 security + 1156 graph) 11/13 scanners ran 82nd percentile · Python · large (100-500K LoC) System graph score 45 (higher by 41)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v2 · last Δ +0.1 (diff) · 493 actionable findings from 2 signal sources. 399 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 · 419 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	87.0	0.20	17.40
`documentation_score`	100.0	0.15	15.00
`practices_score`	100.0	0.15	15.00
`code_quality`	45.0	0.10	4.50
Overall		1.00	85.9

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 116 Medium 83 Low 206 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 74 System graph 419 Crowd 0 Layer: Software 73 Quality 198 Security 86 Cicd 18 Frontend 35 Network 1 Hardware 18 Api 64

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.

Duplicates & near-duplicates 5 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.

5 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 9 places
low Near-duplicate function bodies in 8 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

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 `test_vm_legacy` in libs/python/cua-sandbox/tests/t…

View all legacy markers findings →

Commented-out code 43 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 docs/scripts/modal_app.py:451
info Commented-code block (5 lines) in scripts/docs-generators/cua-driver.ts:645
info Commented-code block (7 lines) in libs/cuabot/src/mcp/overlay-cursor.py:286
info Commented-code block (5 lines) in libs/cua-bench/cua_bench/batch/gcp.py:488
info Commented-code block (5 lines) in libs/cua-bench/cua_bench/runner/task_runner.p…
info Commented-code block (7 lines) in libs/cua-bench/cua_bench/scripts/dump_task_re…
info Commented-code block (7 lines) in libs/cua-bench/cua_bench/scripts/dump_task_re…
info Commented-code block (6 lines) in libs/cua-bench/cua_bench/agents/opencua_agent…
info Commented-code block (5 lines) in libs/cua-bench/cua_bench/trainer/off_policy/t…
info Commented-code block (11 lines) in libs/cua-bench/tasks/winarena_adapter/evalua…
info Commented-code block (7 lines) in libs/cua-bench/tasks/winarena_adapter/evaluat…
info Commented-code block (5 lines) in libs/cua-bench/tasks/winarena_adapter/evaluat…

View all commented-out code findings →

Config drift 10 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.

10 matching findings on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/mirrors-prettier` pin… .pre-commit-config.yaml:2
low File has no detected symbols: docs/source.config.ts
low File has no detected symbols: docs/src/app/layout.config.tsx
low File has no detected symbols: libs/typescript/playground/tsdown.config.ts
low File has no detected symbols: libs/typescript/agent/tsdown.config.ts
low File has no detected symbols: libs/typescript/agent/vitest.config.ts
low File has no detected symbols: libs/typescript/computer/tsdown.config.ts
low File has no detected symbols: libs/typescript/computer/vitest.config.ts
low File has no detected symbols: libs/typescript/core/tsdown.config.ts
low File has no detected symbols: libs/typescript/core/vitest.config.ts

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/1ca50965-4f85-4a66-89b3-c1d72003efb2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1ca50965-4f85-4a66-89b3-c1d72003efb2/

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.