ESP32 iPhone Agent
Website
Let an AI model use a real iPhone with a $7 ESP32: AirPlay eyes, USB HID hands, any OpenAI-compatible vision model. No Mac, no developer account, no jailbreak.
Is ESP32 iPhone Agent safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare ESP32 iPhone Agent
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: ESP32 iPhone Agent scores 26.6/100 (Grade D), ranked #1360 of 1387 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 56% of recent commits are signed; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How ESP32 iPhone Agent could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +44.3 → 70.9 B · #14 of 48
- Sign every commit56% signed today +1.1 → 27.7 D · #45 of 48
Chain of custody
Scanners check what the code says. This traces who ships ESP32 iPhone Agent and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/onehumanbeing/esp32-iphone-agent, MIT, last pushed 2026-11-10. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages None
No registry package. ESP32 iPhone Agent is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of ESP32 iPhone Agent.
Evidence behind this score
Coverage D: 1 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues ESP32 iPhone Agent’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How ESP32 iPhone Agent compares in Browser & Computer Use
- #43 ScaleCUA 30.0 +3.4
- #44 PyWinAssistant 29.5 +2.9
- #45 ESP32 iPhone Agent 26.6 this agent
- #46 Mika 24.3 −2.3
- #47 Open Operator 22.6 −4.0
Bars show each HVTrust score; the tick marks ESP32 iPhone Agent’s 26.6.
Where the 26.6 comes from
HVTrust dimensions vs the Browser & Computer Use average
26.6 / 100 · 50.0% confidenceESP32 iPhone Agent Browser & Computer Use average (48 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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →
Activity & Reach
Analysis
Activity Inputs
85.2 / 100Common questions about ESP32 iPhone Agent
Does ESP32 iPhone Agent publish package provenance?
Does ESP32 iPhone Agent have an OpenSSF Scorecard?
Is ESP32 iPhone Agent actively maintained?
What license does ESP32 iPhone Agent use?
Are ESP32 iPhone Agent'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.
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
Maintain ESP32 iPhone Agent?
For maintainers
HVTrust scores ESP32 iPhone Agent 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/esp32-iphone-agent)
<a href="https://hvtracker.net/agents/esp32-iphone-agent"><img src="https://hvtracker.net/badge/esp32-iphone-agent.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON