updated 2026-11-10 04:07 UTC

agent-device

Repository Website

Open source device layer for AI coding agents: a CLI, MCP server, and typed Node.js API to control mobile, web, TV, and desktop apps on devices and simulators, locally or in the cloud.

Browser & Computer Use TypeScript Listed MIT

Is agent-device safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.5 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare agent-device

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

Pick any agent to compare →
Suggest a correction

In detail: agent-device scores 92.2/100 (Grade A), ranked #12 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.5/10; 100% of recent commits are signed; no published advisory affects its latest release (agent-device); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How agent-device 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 agent-device 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/callstack/agent-device, MIT, last pushed 2026-11-10. 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.5/10 (scanned Oct 29, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked and attested

    • npm agent-device Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: agent-device 0.21.36. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-10-11 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 6.4/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 agent-device’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 agent-device compares in Browser & Computer Use

  1. #1 agent-device 92.2 this agent
  2. #2 OpenClaw 91.3 −0.9
  3. #3 Agent Browser 91.3 −0.9
  4. #4 Stagehand 91.1 −1.1
  5. #5 Browser Harness 90.5 −1.7

Bars show each HVTrust score; the tick marks agent-device’s 92.2.

Where the 92.2 comes from

HVTrust dimensions vs the Browser & Computer Use average

92.2 / 100 · 100.0% confidence

agent-device Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.6 / 25
10.3 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.0 / 17
2.0 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
8.0 above avg 12.0
AdoptionLog-scaled stars · package downloads
16.7 / 20
5.5 above avg 11.2

Quick Trust Read

What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Recent Changes
2026-10-11
Provenance Added
Package provenance attestation detected
2026-10-11
Grade Changed
Trust grade B → A
2026-10-11
Rank Moved
Rank rose 165 spots (#182 → #17)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with OpenClaw
View Browser & Computer Use Report missing data
84.4
Activity sub-score · out of 100
#1
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 today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
5.3k
Forks
388
Last Push
2026-11-10
today
Commits (4 wk)
678
Downloads (7d)
669,888
npm
HN mentions (30d)
—
Open Issues
94
Rank Change
▲1
was #13

Analysis

Activity Inputs

84.4 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.0 / 20

Common questions about agent-device

Public supply-chain signals for agent-device are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but agent-device carries less obvious unverified-evidence risk than projects with thin signals.
Does agent-device publish package provenance?
Yes. agent-device's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does agent-device have an OpenSSF Scorecard?
agent-device has an OpenSSF Scorecard score of 6.5/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 agent-device actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does agent-device use?
agent-device ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are agent-device's commits signed?
100% of the last 100 commits to agent-device 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 agent-device head-to-head

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

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
agent-device 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
high confidence
Declared
Declared 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 agent-device'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-11
Provenance Added
Package provenance attestation detected
2026-10-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain agent-device?

For maintainers

HVTrust scores agent-device 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 18HVTrust 11Grade 9Scorecard 1Delisted 1Listed 1MCP 1Surface 1Provenance 1
2026-10-11
Provenance Added
Package provenance attestation detected
2026-10-11
Grade Changed
Trust grade B → A
2026-10-11
Rank Moved
Rank rose 165 spots (#182 → #17)
2026-10-11
HVTrust Changed
HVTrust up 12.4pts (78.7 → 91.1)
2026-10-07
Grade Changed
Trust grade A → B
2026-10-07
Rank Moved
Rank dropped 22 spots (#153 → #175)
2026-10-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-26
Grade Changed
Trust grade B → A
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 422 spots (#568 → #146)
2026-09-23
HVTrust Changed
HVTrust up 43.9pts (35.8 → 79.7)
2026-09-22
Newly Listed
First tracked at rank #568
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Grade Changed
Trust grade C → B
2026-09-05
Rank Moved
Rank rose 640 spots (#769 → #129)
2026-09-05
HVTrust Changed
HVTrust up 29.1pts (50.4 → 79.5)
2026-09-04
Rank Moved
Rank dropped 26 spots (#743 → #769)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank dropped 36 spots (#707 → #743)
2026-09-02
Grade Changed
Trust grade B → D
2026-09-02
Rank Moved
Rank dropped 604 spots (#103 → #707)
2026-09-02
HVTrust Changed
HVTrust down 29.4pts (79.3 → 49.9)
2026-08-31
Grade Changed
Trust grade C → B
2026-08-31
Rank Moved
Rank rose 507 spots (#607 → #100)
2026-08-31
HVTrust Changed
HVTrust up 29.1pts (50.2 → 79.3)
2026-08-30
Scorecard Added
OSSF Scorecard: 6.4/10
2026-08-30
Grade Changed
Trust grade D → C
2026-08-30
Rank Moved
Rank rose 83 spots (#690 → #607)
2026-08-30
HVTrust Changed
HVTrust up 4.3pts (45.9 → 50.2)
2026-08-29
Rank Moved
Rank dropped 41 spots (#649 → #690)
2026-08-28
Rank Moved
Rank dropped 19 spots (#630 → #649)
2026-08-27
Rank Moved
Rank dropped 13 spots (#617 → #630)
2026-08-26
Rank Moved
Rank dropped 98 spots (#519 → #617)
2026-08-24
Rank Moved
Rank rose 281 spots (#803 → #522)
2026-08-24
HVTrust Changed
HVTrust up 18.7pts (27.2 → 45.9)
2026-08-22
Rank Moved
Rank dropped 278 spots (#525 → #803)
2026-08-22
HVTrust Changed
HVTrust down 18.5pts (45.7 → 27.2)
2026-08-19
Rank Moved
Rank rose 282 spots (#808 → #526)
2026-08-19
HVTrust Changed
HVTrust up 18.5pts (27.1 → 45.6)
2026-08-17
Rank Moved
Rank dropped 285 spots (#523 → #808)
2026-08-17
HVTrust Changed
HVTrust down 18.6pts (45.7 → 27.1)
2026-08-13
Rank Moved
Rank rose 277 spots (#791 → #514)
2026-08-13
HVTrust Changed
HVTrust up 18.6pts (27.1 → 45.7)
GitHub → Website → npm: agent-device

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 92.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/agent-device.svg)](https://hvtracker.net/agents/agent-device)
HTML:
<a href="https://hvtracker.net/agents/agent-device"><img src="https://hvtracker.net/badge/agent-device.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