Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for mobile developers, QA engineers, and agent builders who want a smaller, explicit Android control layer instead of a full device cloud or a hidden accessibility stack.
Who should use it
Who should skip it
Skip yang1ming/android-harness if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
yang1ming/android-harness is tracked by RepoRadar as a automation tool in the Testing & QA section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. The standout signals for yang1ming/android-harness are open-source/build quality (8.4) and workflow potential (8.4), while maturity (5.8) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned yang1ming/android-harness a composite score of 8.0 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It can send taps, text, and file operations to authorized devices over ADB so the first runs should stay on emulators or test phones with seeded accounts; The project is still alpha and some richer text-input or OCR paths depend on optional plugins that teams should audit before using on shared devices.