Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for mobile teams that want agents to verify the app they just built instead of stopping at code generation and hoping the UI works.
Who should use it
Who should skip it
Skip lycorp-jp/sim-use unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
lycorp-jp/sim-use is tracked by RepoRadar as an agent project in the Agents and Automation section. First seen 2026-06-29; the source record was last checked on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for lycorp-jp/sim-use are workflow potential (9.8) and practical usefulness (9.0), while momentum (6.0) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The lycorp-jp/sim-use record combines a 8.3/10 composite score with separate popularity (1.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Agents can tap, type, and trigger real flows on simulators or attached devices, so the first evaluation should stay on throwaway accounts and non-production devices; Android support requires installing the bridge APK and expanding device-control surface area, so teams should review the trust boundary before connecting real handsets.