Sim

Build, deploy, and orchestrate AI agents. Sim is the central intelligence layer for your AI workforce.

Workflow Platforms TypeScript Grade B Listed Apache-2.0
66.3/100
Rank #204 of 1283
Compare Sim

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-12 · 0d ago
Recent change
Rank +1

Is Sim safe? Sim scores 66.3/100 (Grade B), ranked #204 of 1283 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 6.0/10; 100% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 17 spots (#207 → #224)
2026-08-08
Rank Moved
Rank dropped 31 spots (#159 → #190)
2026-07-14
Rank Moved
Rank dropped 11 spots (#149 → #160)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
93.4
Activity sub-score · out of 100
#10

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

Signals refreshed 2026-08-12 05:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
29.4k
Forks
3.8k
Last Push
2026-08-12
today
Commits (4 wk)
661
Downloads (7d)
HN mentions (30d)
Open Issues
116
Rank Change
▲3
was #207

Analysis

HVTrust Dimensions vs Workflow Platforms

66.3 / 100 · 100.0% confidence

Sim Workflow Platforms average (24 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
2.1 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
13.6 / 17
1.2 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
1.8 above avg 18.2
AdoptionLog-scaled stars · package downloads
10.7 / 20
2.2 below avg 12.9

Activity Inputs

93.4 / 100
StarsRepository reach
26.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
OpenSSF Scorecard · scanned Aug 11, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 6
SAST 9
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Sim safe?

Sim has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Sim publish package provenance?
No published build provenance is currently detected for Sim. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sim have an OpenSSF Scorecard?
Sim has an OpenSSF Scorecard score of 6.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Sim actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Sim use?
Sim ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sim's commits signed?
100% of the last 100 commits to Sim 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
high confidence
Implemented
Sim appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
7 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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 Sim?

For maintainers

HVTrust scores Sim 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 4Listed 1
2026-08-10
Rank Moved
Rank dropped 17 spots (#207 → #224)
2026-08-08
Rank Moved
Rank dropped 31 spots (#159 → #190)
2026-07-14
Rank Moved
Rank dropped 11 spots (#149 → #160)
2026-07-13
Rank Moved
Rank dropped 20 spots (#129 → #149)
2026-06-24
Newly Listed
First tracked at rank #110

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

Data sources
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