typesafe-computer-use
Computer use for about $0.0002 a step: OCR the screen, classify the next action with TypeSafe, click. macOS.
Is typesafe-computer-use safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare typesafe-computer-use
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: typesafe-computer-use scores 18.9/100 (Grade D), ranked #1384 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; 100% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →
How typesafe-computer-use 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 +39.3 → 58.2 C · #22 of 48
Chain of custody
Scanners check what the code says. This traces who ships typesafe-computer-use 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 Signed
github.com/awlevin/typesafe-computer-use, MIT, last pushed 2026-09-29. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
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. typesafe-computer-use 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 typesafe-computer-use.
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 typesafe-computer-use’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 typesafe-computer-use compares in Browser & Computer Use
- #44 PyWinAssistant 29.5 +10.6
- #45 ESP32 iPhone Agent 26.6 +7.7
- #46 Mika 24.3 +5.4
- #47 Open Operator 22.6 +3.7
- #48 typesafe-computer-use 18.9 this agent
Bars show each HVTrust score; the tick marks typesafe-computer-use’s 18.9.
Where the 18.9 comes from
HVTrust dimensions vs the Browser & Computer Use average
18.9 / 100 · 50.0% confidencetypesafe-computer-use 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
47.7 / 100Common questions about typesafe-computer-use
Does typesafe-computer-use publish package provenance?
Does typesafe-computer-use have an OpenSSF Scorecard?
Is typesafe-computer-use actively maintained?
What license does typesafe-computer-use use?
Are typesafe-computer-use'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 typesafe-computer-use?
For maintainers
HVTrust scores typesafe-computer-use 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/typesafe-computer-use)
<a href="https://hvtracker.net/agents/typesafe-computer-use"><img src="https://hvtracker.net/badge/typesafe-computer-use.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