A · leads
trigger.dev
97.9
16,776 stars · Apache-2.0
Workflow Automation
trigger.dev leads by 10.3 · clear
A · leads
97.9
16,776 stars · Apache-2.0
B
87.6
2,735 stars · MIT
trigger.dev versus yao-meta-skill is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. trigger.dev is written mainly in TypeScript; yao-meta-skill is written mainly in Python. The composite score is 97.9 for trigger.dev and 87.6 for yao-meta-skill.
trigger.dev has 16,776 GitHub stars to yao-meta-skill's 2,735, a gap of 14,041 (6.13×). Forks are 1,534 for trigger.dev and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 76.
Push history: trigger.dev was last pushed on 17 November 2026 (0 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 268 for trigger.dev (0.016 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
trigger.dev is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. yao-meta-skill is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for trigger.dev and 96 for yao-meta-skill. This is a procurement signal, not legal advice.
In Workflow Automation, both trigger.dev (16,776 stars) and yao-meta-skill (2,735 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: trigger.dev is open source, yao-meta-skill is open source.
The lead is split. trigger.dev is furthest ahead on fork community (100 to 76), while yao-meta-skill is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.9 against yao-meta-skill at 87.6, a 10.3 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | trigger.dev | yao-meta-skill |
|---|---|---|
| GitHub stars | 16,776 | 2,735 |
| Forks | 1,534 | 254 |
| Open issues | 268 | 3 |
| Adoption | 100 | 81 |
| Activity | 100 | 92 |
| Community | 100 | 76 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.6 |
Trigger.dev – build and deploy durable AI agents and workflows
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
trigger.dev has more GitHub stars: 16,776 versus 2,735 for yao-meta-skill. The gap is 14,041 stars.
trigger.dev was pushed more recently: 17 November 2026 versus 09 November 2026 for yao-meta-skill. That is 8 days apart.
Yes. This catalog marks both trigger.dev and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
trigger.dev is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. yao-meta-skill is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
trigger.dev scores 97.9 and yao-meta-skill scores 87.6. This page calls that a clear lead for trigger.dev.