ultraworkers/claw-code

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.

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

Scan timing: clone 11.56s · analysis 6.71s · 13.6 MB · GitHub API rate-limit (preflight)

https://github.com/ultraworkers/claw-code · scanned 2026-06-05 04:30 UTC (5 hours, 52 minutes ago) · 10 languages

179 findings (91 legacy + 88 scanner) 20th percentile · Rust · large (100-500K LoC) Scanner says 72 (lower by 13)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 hours, 51 minutes ago · v2 · 135 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

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	35.8	0.25	8.95
`testing_score`	51.0	0.20	10.20
`documentation_score`	84.0	0.15	12.60
`practices_score`	85.0	0.15	12.75
`code_quality`	38.9	0.10	3.89
Overall		1.00	58.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 63 Medium 10 Low 42 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 91 9-layer 44 Crowd 0 Layer: Cicd 14 Quality 70 Software 40 Security 5 Api 1 Hardware 4 Frontend 1

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.

Fragile runtime 49 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium [COMP001] High cognitive complexity: Function `validate_board` has cognitive co… .omx/cc2/render_board_md.py:75
medium [COMP001] High cognitive complexity: Function `validate_command_examples` has c… .github/scripts/check_release_readiness.py:133
medium Agent auto-approve or skip-permissions mode is easy to enable rust/README.md:128
medium Agent auto-approve or skip-permissions mode is easy to enable rust/.claude/sessions/session-1775009841982.json:1
medium Bare except continues silently scripts/generate_cc2_board.py:102
medium Average file size is 656 lines (recommend <300)
info [MINED062] Python Dataclass No Fields: @dataclass over an empty class — unfinis… src/path_scope.py:24
info [MINED066] Rust Panic Macro: panic!() unwinds the stack. Use Result for recover… rust/crates/runtime/src/mcp_client.rs:173
info [MINED066] Rust Panic Macro: panic!() unwinds the stack. Use Result for recover… rust/crates/runtime/src/git_context.rs:320
info [MINED066] Rust Panic Macro: panic!() unwinds the stack. Use Result for recover… rust/crates/api/src/client.rs:244
info [MINED059] Rust Expect In Prod: .expect(...) panics same as unwrap with a custo… rust/crates/compat-harness/src/lib.rs:324
info [MINED059] Rust Expect In Prod: .expect(...) panics same as unwrap with a custo… rust/crates/api/src/sse.rs:142

View all fragile runtime findings →

Config drift 1 finding

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.

1 matching finding on this repo

low Very large file: rust/crates/runtime/src/config.rs (3826 lines)

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/8cfe9283-d3dd-47e9-97dc-f9c53760eeed/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8cfe9283-d3dd-47e9-97dc-f9c53760eeed/

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.