A
CodeMachine-CLI
74.8
2,516 stars · Apache-2.0
Workflow Automation
trigger.dev leads by 23.1 · decisive
A
74.8
2,516 stars · Apache-2.0
B · leads
97.9
16,776 stars · Apache-2.0
CodeMachine-CLI versus trigger.dev is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 74.8 for CodeMachine-CLI and 97.9 for trigger.dev.
trigger.dev has 16,776 GitHub stars to CodeMachine-CLI's 2,516, a gap of 14,260 (6.67×). Forks are 234 for CodeMachine-CLI and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 74 versus 100.
Push history: CodeMachine-CLI was last pushed on 25 February 2026 (264 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for CodeMachine-CLI (0.004 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.
Both CodeMachine-CLI and trigger.dev are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both CodeMachine-CLI (2,516 stars) and trigger.dev (16,776 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: CodeMachine-CLI is open source, trigger.dev is open source.
The lead is split. CodeMachine-CLI is furthest ahead on issue health (96 to 84), while trigger.dev is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.9 against CodeMachine-CLI at 74.8, a 23.1 point decisive 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 | CodeMachine-CLI | trigger.dev |
|---|---|---|
| GitHub stars | 2,516 | 16,776 |
| Forks | 234 | 1,534 |
| Open issues | 11 | 268 |
| Adoption | 80 | 100 |
| Activity | 36 | 100 |
| Community | 74 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 74.8 | 97.9 |
CodeMachine is an open-source tool that orchestrates AI coding agents into repeatable, long-running workflows. ⚡️
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 2,516 for CodeMachine-CLI. The gap is 14,260 stars.
trigger.dev was pushed more recently: 17 November 2026 versus 25 February 2026 for CodeMachine-CLI. That is 264 days apart.
Yes. This catalog marks both CodeMachine-CLI and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
CodeMachine-CLI 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
trigger.dev scores 97.9 and CodeMachine-CLI scores 74.8. This page calls that a decisive lead for trigger.dev.