Sim vs Trigger.dev
An independent, evidence-based trust comparison of Sim and Trigger.dev, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Trigger.dev leads on trust — 90.9/100 (Grade A) vs 65.3/100 (Grade B), a 25.6-point gap. Full breakdown below.
| Signal | Simsimstudioai/sim | Trigger.devtriggerdotdev/trigger.dev |
|---|---|---|
| HVTrust score | 65.3 | 90.9 |
| Evidence grade | B | A |
| Coverage grade | C | B |
| Overall rank | #260 | #8 |
| Rank in Workflow Platforms | #9 | #1 |
| GitHub stars | 29.5k | 16.2k |
| Last updated | today | 1d ago |
| Build provenance | No | Yes |
| OSSF Scorecard | 5.5 / 10 | 6.6 / 10 |
| License | Apache-2.0 | Apache-2.0 |
| Downloads | — | 608k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 11.9 | 20.7 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 13.2 | 14.1 |
| Maintenance / 20 | 20.0 | 19.9 |
| Adoption / 20 | 10.7 | 17.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 7 — Anthropic, Browserbase, E2B, … | 4 — Anthropic, OpenAI, Postgres, … |
| Requires API keys | No | No |
| Plugin surface | — | extensions |
| Provenance drift | — | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →