Peekaboo

Peekaboo is a macOS CLI & optional MCP server that enables AI agents to capture screenshots of applications, or the enti

Browser & Computer Use Swift Grade D Listed MIT
49.3/100
Rank #785 of 1320
Compare Peekaboo

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-03 · 1d ago
Recent change
Rank +4

Is Peekaboo safe? Peekaboo scores 49.3/100 (Grade D), ranked #785 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 95% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 19 spots (#766 → #785)
2026-09-03
Grade Changed
Trust grade B → D
2026-09-03
Rank Moved
Rank dropped 622 spots (#144 → #766)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
84.2
Activity sub-score · out of 100
#25

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 13:33 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
5.1k
Forks
393
Last Push
2026-09-03
yesterday
Commits (4 wk)
391
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼19
was #766

Analysis

HVTrust Dimensions vs Browser & Computer Use

49.3 / 100 · 67.0% confidence

Peekaboo Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
3.2 above avg 9.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
2.1 above avg 11.7
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.9 above avg 13.0
AdoptionLog-scaled stars · package downloads
8.9 / 20
1.5 below avg 10.4

Activity Inputs

84.2 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.2 / 10
OpenSSF Scorecard · scanned Aug 27, 2026
Signed Commits
95%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 8
Security-Policy 4
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 10

Is Peekaboo safe?

Public trust evidence for Peekaboo is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Peekaboo publish package provenance?
No published build provenance is currently detected for Peekaboo. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Peekaboo have an OpenSSF Scorecard?
Peekaboo has an OpenSSF Scorecard score of 6.2/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 1 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?
95% 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.

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

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
Rank 5HVTrust 2Grade 2Listed 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 19 spots (#766 → #785)
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)
2026-08-10
Newly Listed
First tracked at rank #569

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.3 Grade D
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.3 · Raw JSON