A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 3.6 · narrow
A · leads
91.0
210,804 stars · Sustainable Use License
B
87.4
24,177 stars · MIT
n8n 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. n8n is written mainly in TypeScript; semantic-release is written mainly in JavaScript. The composite score is 91.0 for n8n and 87.4 for semantic-release.
n8n has 210,804 GitHub stars to semantic-release's 24,177, a gap of 186,627 (8.72×). Forks are 61,571 for n8n and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 68.
Push history: n8n 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 1,266 for n8n (0.006 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. 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 38 for n8n and 96 for semantic-release. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 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: n8n is freemium, semantic-release is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 68), while semantic-release is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against semantic-release at 87.4, a 3.6 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 | n8n | semantic-release |
|---|---|---|
| GitHub stars | 210,804 | 24,177 |
| Forks | 61,571 | 1,807 |
| Open issues | 1,266 | 410 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 68 |
| Issue health | 84 | 84 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 87.4 |
n8n is a workflow automation product with a node canvas, self-hosting, and a paid cloud. Its code is source-available under a sustainable-use license, not an OSI open-source license.
📦🚀 Fully automated version management and package publishing
n8n has more GitHub stars: 210,804 versus 24,177 for semantic-release. The gap is 186,627 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both n8n and semantic-release as self-hostable. Confirm each project's deploy docs before you plan a migration.
n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. 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.
n8n scores 91.0 and semantic-release scores 87.4. This page calls that a narrow lead for n8n.