updated 2026-10-09 08:15 UTC

OpenHands

Repository Website

🙌 OpenHands: AI-Driven Development

Coding Agents TypeScript Listed MIT

Is OpenHands safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 100%
Last push today
Advisories None known
Compare OpenHands

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OpenHands scores 74.9/100 (Grade B), ranked #238 of 1371 tracked open-source AI agent projects, on evidence coverage A (5 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 100% of recent commits are signed; no published advisory affects its latest release (openhands-ai); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenHands 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 OpenHands 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/OpenHands/OpenHands, MIT, last pushed 2026-10-09. 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 4.2/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • PyPI openhands-ai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: openhands-ai 1.11.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-09-03 License changed from NOASSERTION to MIT

Evidence behind this score

Coverage A: 5 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues OpenHands’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 OpenHands compares in Coding Agents

  1. #9 oh-my-pi 83.8 +8.9
  2. #10 Gemini CLI 76.6 +1.7
  3. #11 OpenHands 74.9 this agent
  4. #12 Ouroboros (Agent OS) 74.2 −0.7
  5. #13 Tura 72.8 −2.1

Bars show each HVTrust score; the tick marks OpenHands’s 74.9.

Where the 74.9 comes from

HVTrust dimensions vs the Coding Agents average

74.9 / 100 · 100.0% confidence

OpenHands Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.2 / 25
1.4 above avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
0.5 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.6 above avg 14.4
AdoptionLog-scaled stars · package downloads
19.1 / 20
7.2 above avg 11.9

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-30
Rank Moved
Rank dropped 12 spots (#223 → #235)
2026-09-23
Rank Moved
Rank dropped 133 spots (#91 → #224)
2026-09-21
Rank Moved
Rank rose 137 spots (#227 → #90)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Compare with another agent Get email alerts for OpenHands View Coding Agents Report missing data
98.7
Activity sub-score · out of 100
#11
In Coding Agents

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

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
90.3k
Forks
12.0k
Last Push
2026-10-09
today
Commits (4 wk)
338
Downloads (7d)
271,251
pypi
HN mentions (30d)
3
Open Issues
504
Rank Change
▼1
was #237

Analysis

Activity Inputs

98.7 / 100
StarsRepository reach
29.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
19.0 / 20

Common questions about OpenHands

OpenHands has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does OpenHands publish package provenance?
No published build provenance is currently detected for OpenHands. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenHands have an OpenSSF Scorecard?
OpenHands has an OpenSSF Scorecard score of 4.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 OpenHands actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does OpenHands use?
OpenHands ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenHands's commits signed?
100% of the last 100 commits to OpenHands 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium 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

Maintain OpenHands?

For maintainers

HVTrust scores OpenHands 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

Public Actions

Actions (30d)
100
Merged (30d)
82
Merge rate
82%
Top repos (sampled)

Action counts reflect activity on public repos where this agent left detectable fingerprints. Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query). Methodology described in the Provenance Profile spec.

Reputation Timeline

Signal history
Rank 11HVTrust 2License 1
2026-09-30
Rank Moved
Rank dropped 12 spots (#223 → #235)
2026-09-23
Rank Moved
Rank dropped 133 spots (#91 → #224)
2026-09-21
Rank Moved
Rank rose 137 spots (#227 → #90)
2026-09-07
Rank Moved
Rank dropped 15 spots (#210 → #225)
2026-09-06
Rank Moved
Rank dropped 37 spots (#173 → #210)
2026-09-05
Rank Moved
Rank dropped 52 spots (#121 → #173)
2026-09-03
License Changed
License changed from NOASSERTION to MIT
2026-09-03
Rank Moved
Rank rose 52 spots (#171 → #119)
2026-09-03
HVTrust Changed
HVTrust up 5.0pts (72.7 → 77.7)
2026-08-31
Rank Moved
Rank dropped 23 spots (#140 → #163)
2026-08-26
Rank Moved
Rank dropped 15 spots (#119 → #134)
2026-07-28
Rank Moved
Rank dropped 20 spots (#86 → #106)
2026-07-28
HVTrust Changed
HVTrust down 3.0pts (73.2 → 70.2)
2026-07-13
Rank Moved
Rank dropped 10 spots (#66 → #76)
GitHub → Website → PyPI: openhands-ai

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API · GitHub Search API (fingerprint actions)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON