A · leads
Node-RED
97.9
23,852 stars · Apache-2.0
Workflow Automation
Node-RED leads by 1.3 · narrow
A · leads
97.9
23,852 stars · Apache-2.0
B
96.6
24,177 stars · MIT
Node-RED versus semantic-release 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 JavaScript. The composite score is 97.9 for Node-RED and 96.6 for semantic-release.
semantic-release has 24,177 GitHub stars to Node-RED's 23,852, a gap of 325 (1.01×). Forks are 4,033 for Node-RED and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 90.
Push history: Node-RED was last pushed on 17 November 2026 (0 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 355 for Node-RED (0.015 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. semantic-release 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 Node-RED and 96 for semantic-release. This is a procurement signal, not legal advice.
In Workflow Automation, both Node-RED (23,852 stars) and semantic-release (24,177 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: Node-RED is open source, semantic-release is open source.
The lead is split. Node-RED is furthest ahead on fork community (100 to 90), while semantic-release is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.
Node-RED finishes ahead at 97.9 against semantic-release at 96.6, a 1.3 point narrow 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 | Node-RED | semantic-release |
|---|---|---|
| GitHub stars | 23,852 | 24,177 |
| Forks | 4,033 | 1,807 |
| Open issues | 355 | 410 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.6 |
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.
📦🚀 Fully automated version management and package publishing
semantic-release has more GitHub stars: 24,177 versus 23,852 for Node-RED. The gap is 325 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Node-RED and semantic-release as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. semantic-release 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.
Node-RED scores 97.9 and semantic-release scores 96.6. This page calls that a narrow lead for Node-RED.