A · leads
airflow
96.5
47,513 stars · Apache-2.0
Workflow Automation
airflow leads by 4.0 · narrow
A · leads
96.5
47,513 stars · Apache-2.0
B
92.5
24,177 stars · MIT
airflow 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. airflow is written mainly in Python; semantic-release is written mainly in JavaScript. The composite score is 96.5 for airflow and 92.5 for semantic-release.
airflow has 47,513 GitHub stars to semantic-release's 24,177, a gap of 23,336 (1.97×). Forks are 18,381 for airflow and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 76.
Push history: airflow 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,931 for airflow (0.041 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
airflow 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 airflow and 96 for semantic-release. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 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: airflow is open source, semantic-release is open source.
The lead is split. airflow is furthest ahead on fork community (100 to 76), while semantic-release is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
airflow finishes ahead at 96.5 against semantic-release at 92.5, a 4.0 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 | airflow | semantic-release |
|---|---|---|
| GitHub stars | 47,513 | 24,177 |
| Forks | 18,381 | 1,807 |
| Open issues | 1,931 | 410 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 92.5 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
📦🚀 Fully automated version management and package publishing
airflow has more GitHub stars: 47,513 versus 24,177 for semantic-release. The gap is 23,336 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and semantic-release as self-hostable. Confirm each project's deploy docs before you plan a migration.
airflow 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.
airflow scores 96.5 and semantic-release scores 92.5. This page calls that a narrow lead for airflow.