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 a mobile agent runtime in the Agents and Automation section. It was first seen on 2026-06-29 and last updated 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 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 lycorp-jp/sim-use a composite score of 8.3 out of 10, placing it in the Gold 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 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.