OpenManus
No fortress, purely open ground. OpenManus is Coming.
Is OpenManus safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare OpenManus
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: OpenManus scores 30.0/100 (Grade D), ranked #1306 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 24% of recent commits are signed; last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →
How OpenManus 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 +33.7 → 63.7 C · #45 of 129
- Sign every commit24% signed today +2.5 → 32.5 D · #112 of 129
Chain of custody
Scanners check what the code says. This traces who ships OpenManus 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 Partly signed
github.com/FoundationAgents/OpenManus, MIT, last pushed 2026-09-30. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
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. OpenManus is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-10-02 Provenance drift warning cleared (now: not_applicable)
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks (missing)
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues OpenManus’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 OpenManus compares in Agent Frameworks
- #114 xpander.ai 30.9 +0.9
- #115 AutoAgent 30.4 +0.4
- #116 OpenManus 30.0 this agent
- #117 cashclaw 29.9 −0.1
- #118 Lingxi 29.8 −0.2
Bars show each HVTrust score; the tick marks OpenManus’s 30.0.
Where the 30.0 comes from
HVTrust dimensions vs the Agent Frameworks average
30.0 / 100 · 67.0% confidenceOpenManus Agent Frameworks average (129 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
71.1 / 100Common questions about OpenManus
Does OpenManus publish package provenance?
Does OpenManus have an OpenSSF Scorecard?
Is OpenManus actively maintained?
What license does OpenManus use?
Are OpenManus'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 →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to OpenManus'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.
Maintain OpenManus?
For maintainers
HVTrust scores OpenManus 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/openmanus)
<a href="https://hvtracker.net/agents/openmanus"><img src="https://hvtracker.net/badge/openmanus.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license) · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON