Peekaboo
Peekaboo is a macOS CLI & optional MCP server that enables AI agents to capture screenshots of applications, or the entire system, with optional visual question answering through local or remote AI models.
Is Peekaboo safe? Strong public trust posture, backed by multiple independent signals.
Compare Peekaboo
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: Peekaboo scores 76.9/100 (Grade B), ranked #188 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; 99% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Peekaboo compares in Browser & Computer Use
- #7 Camofox Browser 81.7 +4.8
- #8 agent-device 80.1 +3.2
- #9 Peekaboo 76.9 this agent
- #10 Browser4 75.0 −1.9
- #11 Cua 74.3 −2.6
Bars show each HVTrust score; the tick marks Peekaboo’s 76.9.
Where the 76.9 comes from
HVTrust dimensions vs the Browser & Computer Use average
76.9 / 100 · 100.0% confidencePeekaboo 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 B 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
84.4 / 100Supply Chain Trust
Common questions about Peekaboo
Does Peekaboo publish package provenance?
Does Peekaboo have an OpenSSF Scorecard?
Is Peekaboo actively maintained?
What license does Peekaboo use?
Are Peekaboo'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
Detected changes to Peekaboo'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 Peekaboo?
For maintainers
HVTrust scores Peekaboo 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/peekaboo)
<a href="https://hvtracker.net/agents/peekaboo"><img src="https://hvtracker.net/badge/peekaboo.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