agent-device
Mobile app automation and verification for AI coding agents. CLI, MCP server, and typed Node.js API for iOS, Android, HarmonyOS, TV, web, macOS, and Linux.
Is agent-device safe? Strong public trust posture, backed by multiple independent signals.
Compare agent-device
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: agent-device scores 80.1/100 (Grade A), ranked #140 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.7/10; 96% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How agent-device compares in Browser & Computer Use
- #6 Skyvern 86.9 +6.8
- #7 Camofox Browser 81.7 +1.6
- #8 agent-device 80.1 this agent
- #9 Peekaboo 76.9 −3.2
- #10 Browser4 75.0 −5.1
Bars show each HVTrust score; the tick marks agent-device’s 80.1.
Where the 80.1 comes from
HVTrust dimensions vs the Browser & Computer Use average
80.1 / 100 · 100.0% confidenceagent-device Browser & Computer Use average (42 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
83.7 / 100Supply Chain Trust
Common questions about agent-device
Does agent-device publish package provenance?
Does agent-device have an OpenSSF Scorecard?
Is agent-device actively maintained?
What license does agent-device use?
Are agent-device's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare agent-device head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to agent-device's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain agent-device?
For maintainers
HVTrust scores agent-device from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/agent-device)
<a href="https://hvtracker.net/agents/agent-device"><img src="https://hvtracker.net/badge/agent-device.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON