updated 2026-11-10 04:07 UTC

Peekaboo

Repository Website by openclaw

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.

Browser & Computer Use Swift Listed MIT

Is Peekaboo safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.8 / 10
Provenance Attested
Signed commits 100%
Last push 2d ago
Advisories None known
Compare Peekaboo

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Peekaboo scores 90.0/100 (Grade A), ranked #28 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.8/10; 100% of recent commits are signed; no published advisory affects its latest release (@steipete/peekaboo); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Peekaboo 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Peekaboo and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/openclaw/Peekaboo, MIT, last pushed 2026-11-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.8/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 4
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 3
    SAST 10
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @steipete/peekaboo 4.9.8. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-10-05 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 6.2/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Peekaboo’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.

Signed credential (JSON) How to verify

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 Peekaboo compares in Browser & Computer Use

  1. #4 Stagehand 91.1 +1.1
  2. #5 Browser Harness 90.5 +0.5
  3. #6 Peekaboo 90.0 this agent
  4. #7 Argent 89.8 −0.2
  5. #8 Skyvern 87.3 −2.7

Bars show each HVTrust score; the tick marks Peekaboo’s 90.0.

Where the 90.0 comes from

HVTrust dimensions vs the Browser & Computer Use average

90.0 / 100 · 100.0% confidence

Peekaboo Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.0 / 25
10.7 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.3 above avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
2.3 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.9 above avg 12.0
AdoptionLog-scaled stars · package downloads
13.4 / 20
2.2 above avg 11.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with agent-device
View Browser & Computer Use Report missing data
84.5
Activity sub-score · out of 100
#6
In Browser & Computer Use

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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
5.5k
Forks
421
Last Push
2026-11-08
2 days ago
Commits (4 wk)
114
Downloads (7d)
2,184
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
=
was #28

Analysis

Activity Inputs

84.5 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.2 / 20

Common questions about Peekaboo

Public supply-chain signals for Peekaboo are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Peekaboo carries less obvious unverified-evidence risk than projects with thin signals.
Does Peekaboo publish package provenance?
Yes. Peekaboo's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Peekaboo have an OpenSSF Scorecard?
Peekaboo has an OpenSSF Scorecard score of 6.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Peekaboo actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Peekaboo use?
Peekaboo ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Peekaboo's commits signed?
100% of the last 100 commits to Peekaboo are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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 Peekaboo head-to-head

Peekaboo vs agent-device → Peekaboo vs OpenClaw → Peekaboo vs Agent Browser →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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 Server Support
high confidence
Implemented
Peekaboo appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-10-05
Provenance Added
Package provenance attestation detected
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 8HVTrust 5Grade 5Scorecard 1Delisted 1Listed 1MCP 1Surface 1Provenance 1
2026-10-05
Provenance Added
Package provenance attestation detected
2026-10-05
Grade Changed
Trust grade B → A
2026-10-05
Rank Moved
Rank rose 178 spots (#202 → #24)
2026-10-05
HVTrust Changed
HVTrust up 13.0pts (76.5 → 89.5)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 388 spots (#574 → #186)
2026-09-23
HVTrust Changed
HVTrust up 41.3pts (35.5 → 76.8)
2026-09-22
Newly Listed
First tracked at rank #574
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 607 spots (#802 → #195)
2026-09-05
HVTrust Changed
HVTrust up 26.0pts (49.3 → 75.3)
2026-09-04
Rank Moved
Rank dropped 36 spots (#766 → #802)
2026-09-03
Grade Changed
Trust grade B → D
2026-09-03
Rank Moved
Rank dropped 622 spots (#144 → #766)
2026-09-03
HVTrust Changed
HVTrust down 25.3pts (74.7 → 49.4)
2026-08-31
Rank Moved
Rank dropped 17 spots (#121 → #138)
2026-08-26
Scorecard Added
OSSF Scorecard: 6.2/10
2026-08-26
Grade Changed
Trust grade D → B
2026-08-26
Rank Moved
Rank rose 477 spots (#585 → #108)
2026-08-26
HVTrust Changed
HVTrust up 31.8pts (42.9 → 74.7)
2026-08-13
Rank Moved
Rank dropped 10 spots (#565 → #575)
GitHub → Website → npm: @steipete/peekaboo

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 90.0 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/peekaboo.svg)](https://hvtracker.net/agents/peekaboo)
HTML:
<a href="https://hvtracker.net/agents/peekaboo"><img src="https://hvtracker.net/badge/peekaboo.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
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.4 · Raw JSON