SimWorld
SimWorld: An Open-ended Realistic Simulator for Autonomous Agents in Physical and Social Worlds
Is SimWorld safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare SimWorld
How does it stack up against its Observability & Evaluation neighbours?
Pick any agent to compare →In detail: SimWorld scores 42.1/100 (Grade D), ranked #1123 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 26% of recent commits are signed; last pushed 2026-06-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How SimWorld compares in Observability & Evaluation
- #19 TruLens 46.7 +4.6
- #20 Ragas 44.5 +2.4
- #21 SimWorld 42.1 this agent
- #22 AgentBench 37.3 −4.8
- #23 Webarena 36.3 −5.8
Bars show each HVTrust score; the tick marks SimWorld’s 42.1.
Where the 42.1 comes from
HVTrust dimensions vs the Observability & Evaluation average
42.1 / 100 · 100.0% confidenceSimWorld Observability & Evaluation average (23 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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
38.7 / 100Supply Chain Trust
Common questions about SimWorld
Does SimWorld publish package provenance?
Does SimWorld have an OpenSSF Scorecard?
Is SimWorld actively maintained?
What license does SimWorld use?
Are SimWorld'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 SimWorld'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 SimWorld?
For maintainers
HVTrust scores SimWorld 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/simworld)
<a href="https://hvtracker.net/agents/simworld"><img src="https://hvtracker.net/badge/simworld.svg" alt="HVTrust"></a>
Other agents in Observability & Evaluation
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON