updated 2026-08-12 05:02 UTC

SimWorld

SimWorld-AI/SimWorld

SimWorld: An Open-ended Realistic Simulator for Autonomous Agents in Physical and Social Worlds

Observability & Evaluation Python Grade D Listed Apache-2.0
17.9/100
Rank #1160 of 1283
Compare SimWorld

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-06-26 · 47d ago
Recent change
New

Is SimWorld safe? SimWorld scores 17.9/100 (Grade D), ranked #1160 of 1283 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; 26% of recent commits are signed; last pushed 2026-06-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#19 TruLens — 44.4 (D) → #20 AgentBench — 37.3 (D) → #21 Webarena — 36.3 (D) → #22 agentacct — 25.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #1158
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.
Refresh maintenance signals The repo was last pushed 47 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for SimWorld View Observability & Evaluation Report missing data
44.6
Activity sub-score · out of 100
#23
In Observability & Evaluation

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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 47 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
750
Forks
78
Last Push
2026-06-26
47 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #1160

Analysis

HVTrust Dimensions vs Observability & Evaluation

17.9 / 100 · 50.0% confidence

SimWorld Observability & Evaluation average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.3 / 25
9.6 below avg 10.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.2 below avg 13.0
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.4 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
8.9 / 20
6.2 below avg 15.1
AdoptionLog-scaled stars · package downloads
6.9 / 20
7.0 below avg 13.9

Activity Inputs

44.6 / 100
StarsRepository reach
17.3 / 30
FreshnessLast push recency
18.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.8 / 20

Supply Chain Trust

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

Is SimWorld safe?

Public trust evidence for SimWorld 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 SimWorld publish package provenance?
No published build provenance is currently detected for SimWorld. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SimWorld have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for SimWorld. 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 SimWorld actively maintained?
Slowing down. Last push was 47 days ago — keep an eye on whether activity resumes.
What license does SimWorld use?
SimWorld ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SimWorld's commits signed?
26% of the last 100 commits to SimWorld 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-10
Newly Listed
First tracked at rank #1158
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

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