AWorld
Search, understand, reproduce, and improve an idea with ease
Is AWorld safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare AWorld
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: AWorld scores 23.1/100 (Grade D), ranked #1367 of 1374 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; 6% of recent commits are signed; last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →
How AWorld 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 +42.4 → 65.5 B · #45 of 130
- Sign every commit6% signed today +2.4 → 25.5 D · #127 of 130
Chain of custody
Scanners check what the code says. This traces who ships AWorld 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/inclusionAI/AWorld, MIT, last pushed 2026-11-04. 6% 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. AWorld 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 AWorld.
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 AWorld’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 AWorld compares in Agent Frameworks
- #126 JARVIS / HuggingGPT 26.5 +3.4
- #127 AIlice 24.1 +1.0
- #128 mcp-agent 23.5 +0.4
- #129 AWorld 23.1 this agent
- #130 AutoAgent 20.4 −2.7
Bars show each HVTrust score; the tick marks AWorld’s 23.1.
Where the 23.1 comes from
HVTrust dimensions vs the Agent Frameworks average
23.1 / 100 · 50.0% confidenceAWorld Agent Frameworks average (130 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
78.4 / 100Common questions about AWorld
Does AWorld publish package provenance?
Does AWorld have an OpenSSF Scorecard?
Is AWorld actively maintained?
What license does AWorld use?
Are AWorld'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
Detected changes to AWorld'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 AWorld?
For maintainers
HVTrust scores AWorld 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/aworld)
<a href="https://hvtracker.net/agents/aworld"><img src="https://hvtracker.net/badge/aworld.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON