coasty-ai/open-computer-use

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.

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 81.45s for a 91.5 MB repo slow.
Repobility's analysis ran in 13.57s after the clone landed.

https://github.com/coasty-ai/open-computer-use · scanned 2026-05-31 01:28 UTC (1 week, 6 days ago) · 10 languages

1664 raw signals (283 security + 1381 graph) 10/13 scanners ran 80th percentile · Typescript · large (100-500K LoC) System graph score 62 (higher by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 6 days ago · v2 · last Δ -0.1 (diff) · 824 actionable findings from 2 signal sources. 167 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 · 706 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	92.0	0.15	13.80
`practices_score`	52.0	0.15	7.80
`code_quality`	45.0	0.10	4.50
Overall		1.00	83.8

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 4 High 202 Medium 108 Low 182 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 118 System graph 706 Crowd 0 Layer: Quality 366 Security 62 Software 79 Cicd 8 Frontend 164 Hardware 4 Api 141

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

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 `calls_legacy` in tests/vm-agent-typing-speed.test.…

View all legacy markers findings →

Commented-out code 184 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 middleware.ts:9
info Commented-code block (8 lines) in electron/electron.vite.config.ts:20
info Commented-code block (7 lines) in electron/playwright.config.ts:4
info Commented-code block (7 lines) in electron/src/renderer/send-flow-integration.t…
info Commented-code block (10 lines) in electron/src/renderer/bugfix-stop-and-input.…
info Commented-code block (5 lines) in electron/src/renderer/machine-busy.test.ts:181
info Commented-code block (5 lines) in electron/src/renderer/auto-expand-on-handoff.…
info Commented-code block (7 lines) in electron/src/renderer/App.tsx:64
info Commented-code block (6 lines) in electron/src/renderer/stores/chat-store.ts:217
info Commented-code block (7 lines) in electron/src/renderer/stores/load-chat.test.t…
info Commented-code block (8 lines) in electron/src/renderer/components/Overlay.tsx:…
info Commented-code block (9 lines) in electron/src/renderer/components/CuaSectionRe…

View all commented-out code findings →

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

11 matching findings on this repo

medium No CI/CD configuration found
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: next.config.ts
low File has no detected symbols: i18n/config.ts
low File has no detected symbols: electron/electron.vite.config.ts
low File has no detected symbols: electron/playwright.config.ts
low File has no detected symbols: electron/tailwind.config.js
low File has no detected symbols: electron/vitest.config.ts
info `truncate` class without `title=` for hover reveal — app/components/schedules/s…
info Commented-code block (8 lines) in electron/electron.vite.config.ts:20
info Commented-code block (7 lines) in electron/playwright.config.ts:4

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/0e944bde-4911-4fc7-bd85-665b19a7e379/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0e944bde-4911-4fc7-bd85-665b19a7e379/

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.