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
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.

coasty-ai/open-computer-use

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

1664 findings (283 legacy + 1381 scanner) 10/13 scanners ran 80th percentile · Typescript · large (100-500K LoC) Scanner says 62 (higher by 22)

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

Complete repo analysis

Last scanned 5 days, 12 hours ago · v2 · last Δ -0.1 (diff) · 995 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
75.9
/100
Repobility
90
283 legacy
9-layer
62
100.0% cov · 712 gaps
Critical
11
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 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 11 High 355 Medium 116 Low 213 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 283 9-layer 712 Crowd 0 Layer: Quality 512 Security 75 Software 82 Cicd 17 Frontend 164 Hardware 4 Api 141

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in app/components/secrets/import-dialog.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in app/components/secrets/import-dialog.tsx:518; move to env var / secrets manager.
app/components/secrets/import-dialog.tsx:518
#2
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:17; move to env var / secrets manager.
lib/import-credentials.ts:17
#3
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:29; move to env var / secrets manager.
lib/import-credentials.ts:29
#4
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:41; move to env var / secrets manager.
lib/import-credentials.ts:41
#5
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:53; move to env var / secrets manager.
lib/import-credentials.ts:53
#6
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:65; move to env var / secrets manager.
lib/import-credentials.ts:65
#7
Possible secret in lib/import-credentials.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in lib/import-credentials.ts:77; move to env var / secrets manager.
lib/import-credentials.ts:77
#8
Blocking `time.sleep(...)` inside `async def execute_command` — docker/ai-desktop/ai_agent_server.py:472
GapSeverity.HIGH Layer.QUALITY score 0.394
Why: high severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in docker/ai-desktop/ai_agent_server.py:472 to prevent hung calls.
docker/ai-desktop/ai_agent_server.py:472
#9
Blocking `time.sleep(...)` inside `async def execute_command` — docker/ai-desktop/ai_agent_server.py:485
GapSeverity.HIGH Layer.QUALITY score 0.394
Why: high severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in docker/ai-desktop/ai_agent_server.py:485 to prevent hung calls.
docker/ai-desktop/ai_agent_server.py:485
#10
Blocking `time.sleep(...)` inside `async def execute_command` — docker/ai-desktop/ai_agent_server.py:498
GapSeverity.HIGH Layer.QUALITY score 0.394
Why: high severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in docker/ai-desktop/ai_agent_server.py:498 to prevent hung calls.
docker/ai-desktop/ai_agent_server.py:498

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.