A · level
cli
96.2
32,362 stars · Apache-2.0
Workflow Automation
Too close to call · 96.2 to 96.9
A · level
96.2
32,362 stars · Apache-2.0
B · level
96.9
23,852 stars · Apache-2.0
cli versus Node-RED is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Rust; Node-RED is written mainly in JavaScript. The composite score is 96.2 for cli and 96.9 for Node-RED.
cli has 32,362 GitHub stars to Node-RED's 23,852, a gap of 8,510 (1.36×). Forks are 1,997 for cli and 4,033 for Node-RED. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 92 versus 100.
Push history: cli was last pushed on 03 November 2026 (14 days ago), and Node-RED was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 355 for Node-RED (0.015 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
Both cli and Node-RED 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 cli (32,362 stars) and Node-RED (23,852 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: cli is open source, Node-RED is open source.
The lead is split. cli is furthest ahead on issue health (96 to 84), while Node-RED is furthest ahead on fork community (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: cli 96.2, Node-RED 96.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | cli | Node-RED |
|---|---|---|
| GitHub stars | 32,362 | 23,852 |
| Forks | 1,997 | 4,033 |
| Open issues | 137 | 355 |
| Adoption | 100 | 97 |
| Activity | 92 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 96.9 |
Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.
Node-RED is a flow-based programming tool from the OpenJS Foundation, widely used to wire APIs, devices, and events. Flows are JSON graphs of nodes that you can version and run on your own host.
cli has more GitHub stars: 32,362 versus 23,852 for Node-RED. The gap is 8,510 stars.
Node-RED was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.
Yes. This catalog marks both cli and Node-RED as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Node-RED 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.
Neither tool clears a one-point margin. cli scores 96.2 and Node-RED scores 96.9.