OpenManus

No fortress, purely open ground. OpenManus is Coming.

Agent Frameworks Python Grade D Listed MIT
31.6/100
Rank #754 of 1308
Compare OpenManus

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-22 · 3d ago
Recent change
No recent signal change

Is OpenManus safe? OpenManus scores 31.6/100 (Grade D), ranked #754 of 1308 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-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Activity Resumed
Activity resumed
2026-08-16
Rank Moved
Rank rose 313 spots (#1069 → #756)
2026-08-16
HVTrust Changed
HVTrust up 12.0pts (19.8 → 31.8)
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
84.4
Activity sub-score · out of 100
#84

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 →

Signals refreshed 2026-08-25 05:32 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
58.1k
Forks
10.1k
Last Push
2026-08-22
3 days ago
Commits (4 wk)
9
Downloads (7d)
38
pypi
HN mentions (30d)
2
Open Issues
275
Rank Change
=
was #754

Analysis

HVTrust Dimensions vs Agent Frameworks

31.6 / 100 · 75.0% confidence

OpenManus Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.2 / 25
6.9 below avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.0 below avg 11.5
Maintenance60% last-push freshness · 40% commit activity
15.8 / 20
1.7 above avg 14.1
AdoptionLog-scaled stars · package downloads
13.6 / 20
2.3 above avg 11.3

Activity Inputs

84.4 / 100
StarsRepository reach
28.6 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
18.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
24%
of last 100 commits verified

Is OpenManus safe?

Public trust evidence for OpenManus 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 OpenManus publish package provenance?
No published build provenance is currently detected for OpenManus. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenManus have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for OpenManus. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is OpenManus actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does OpenManus use?
OpenManus ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenManus's commits signed?
24% of the last 100 commits to OpenManus 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
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Warning
1 package source mismatch detected
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 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.

2026-08-16
Activity Resumed
Activity resumed
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo

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
Rank 21HVTrust 9Drift 1Score 1Fresh 1
2026-08-16
Activity Resumed
Activity resumed
2026-08-16
Rank Moved
Rank rose 313 spots (#1069 → #756)
2026-08-16
HVTrust Changed
HVTrust up 12.0pts (19.8 → 31.8)
2026-08-16
Activity Score Changed
Activity score up 38pts (47 → 85)
2026-08-12
Rank Moved
Rank rose 12 spots (#1082 → #1070)
2026-08-10
Rank Moved
Rank dropped 67 spots (#1010 → #1077)
2026-08-08
Rank Moved
Rank dropped 513 spots (#491 → #1004)
2026-08-06
Rank Moved
Rank dropped 15 spots (#453 → #468)
2026-08-03
Rank Moved
Rank dropped 17 spots (#436 → #453)
2026-07-28
Rank Moved
Rank dropped 18 spots (#416 → #434)
2026-07-14
Rank Moved
Rank dropped 46 spots (#368 → #414)
2026-07-13
Rank Moved
Rank dropped 40 spots (#328 → #368)
2026-06-24
Rank Moved
Rank dropped 35 spots (#276 → #311)
2026-06-23
Rank Moved
Rank dropped 23 spots (#253 → #276)
2026-06-22
Rank Moved
Rank dropped 10 spots (#243 → #253)
2026-06-21
Rank Moved
Rank dropped 17 spots (#226 → #243)
2026-06-16
Rank Moved
Rank rose 12 spots (#223 → #211)
2026-06-16
HVTrust Changed
HVTrust up 10.1pts (17.8 → 27.9)
2026-06-15
Rank Moved
Rank dropped 14 spots (#209 → #223)
2026-06-15
HVTrust Changed
HVTrust down 10.2pts (28.0 → 17.8)
2026-06-13
Rank Moved
Rank rose 13 spots (#222 → #209)
2026-06-13
HVTrust Changed
HVTrust up 10.5pts (17.9 → 28.4)
2026-06-11
Rank Moved
Rank dropped 14 spots (#208 → #222)
2026-06-11
HVTrust Changed
HVTrust down 10.8pts (28.7 → 17.9)
2026-06-10
HVTrust Changed
HVTrust up 10.7pts (18.0 → 28.7)
2026-06-08
Rank Moved
Rank dropped 16 spots (#197 → #213)
2026-06-08
HVTrust Changed
HVTrust down 10.9pts (29.0 → 18.1)
2026-06-07
Rank Moved
Rank rose 13 spots (#210 → #197)
2026-06-07
HVTrust Changed
HVTrust up 10.9pts (18.1 → 29.0)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-06-02
Rank Moved
Rank dropped 17 spots (#176 → #193)
2026-06-01
Rank Moved
Rank dropped 12 spots (#164 → #176)
2026-05-29
HVTrust Changed
HVTrust up 6.7pts (16.0 → 22.7)

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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