OpenHands/OpenHands

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.

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

Scan timing: clone 3.77s · analysis 145.3s · 16.5 MB · GitHub API rate-limit (preflight)

https://github.com/OpenHands/OpenHands · scanned 2026-06-05 07:42 UTC (5 days, 22 hours ago) · 10 languages

1215 raw signals (493 security + 722 graph) 12th percentile · Typescript · large (100-500K LoC) System graph score 59 (higher by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 551 actionable findings from 2 signal sources. 303 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 · 299 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	0.0	0.25	0.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	96.0	0.15	14.40
`practices_score`	100.0	0.15	15.00
`code_quality`	49.6	0.10	4.96
Overall		1.00	63.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 123 Medium 46 Low 223 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 252 System graph 299 Crowd 0 Layer: Quality 226 Security 55 Software 168 Cicd 21 Frontend 23 Network 1 Hardware 6 Api 51

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

6 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 4 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.

4 matching findings on this repo

low Old/deprecated-named symbol `agent_kind_llm_legacy` in enterprise/tests/unit/se…
low Old/deprecated-named symbol `test_gitlab_search_repositories_public_search_lega…
low Old/deprecated-named symbol `mock_result_legacy` in tests/unit/app_server/test_…
low Old/deprecated-named symbol `_get_sandbox_by_session_api_key_legacy` in openhan…

View all legacy markers findings →

Commented-out code 57 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 (7 lines) in frontend/__tests__/conversation-websocket-han…
info Commented-code block (6 lines) in frontend/__tests__/components/features/guards…
info Commented-code block (5 lines) in frontend/__tests__/components/features/onboar…
info Commented-code block (5 lines) in frontend/__tests__/routes/llm-settings.test.t…
info Commented-code block (5 lines) in frontend/__tests__/hooks/mutation/use-new-con…
info Commented-code block (7 lines) in frontend/src/i18n/index.ts:42
info Commented-code block (7 lines) in frontend/src/api/conversation-service/v1-conv…
info Commented-code block (6 lines) in frontend/src/constants/settings-nav.tsx:26
info Commented-code block (5 lines) in frontend/src/utils/websocket-url.ts:45
info Commented-code block (5 lines) in frontend/src/components/v1/chat/messages.tsx:…
info Commented-code block (6 lines) in frontend/src/components/v1/chat/event-content…
info Commented-code block (7 lines) in frontend/src/components/v1/chat/event-content…

View all commented-out code findings →

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

7 matching findings on this repo

high Phantom test coverage: test_update_team_and_users_budget_missing_config enterprise/tests/unit/test_lite_llm_manager.py:834
low File has no detected symbols: frontend/playwright.config.ts
low File has no detected symbols: frontend/vite.config.ts
low File has no detected symbols: frontend/tailwind.config.js
low File has no detected symbols: frontend/__tests__/utils/mcp-config.test.ts
medium Network/subprocess call without timeout or try/except — enterprise/server/confi…
low Old/deprecated-named symbol `enable_v1` in openhands/app_server/server_config/s…

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/3808c140-1460-4c5b-8651-204c3325fe6f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3808c140-1460-4c5b-8651-204c3325fe6f/

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.