A
automa
70.3
21,723 stars · license n/a
Workflow Automation
semantic-release leads by 27.2 · decisive
A
70.3
21,723 stars · license n/a
B · leads
97.5
24,177 stars · MIT
automa 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. automa is written mainly in Vue; semantic-release is written mainly in JavaScript. The composite score is 70.3 for automa and 97.5 for semantic-release.
semantic-release has 24,177 GitHub stars to automa's 21,723, a gap of 2,454 (1.11×). Forks are 2,341 for automa and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 97.
Push history: automa was last pushed on 02 March 2026 (260 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 84 and 84; activity scores are 36 and 100.
automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for automa and 96 for semantic-release. This is a procurement signal, not legal advice.
Only semantic-release is marked self-hostable here (24,177 stars, deploy score 100). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, semantic-release is open source.
The lead is split. automa is furthest ahead on fork community (100 to 97), while semantic-release is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
semantic-release finishes ahead at 97.5 against automa at 70.3, a 27.2 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 | automa | semantic-release |
|---|---|---|
| GitHub stars | 21,723 | 24,177 |
| Forks | 2,341 | 1,807 |
| Open issues | 379 | 410 |
| Adoption | 99 | 100 |
| Activity | 36 | 100 |
| Community | 100 | 97 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 70.3 | 97.5 |
A browser extension for automating your browser by connecting blocks
📦🚀 Fully automated version management and package publishing
semantic-release has more GitHub stars: 24,177 versus 21,723 for automa. The gap is 2,454 stars.
semantic-release was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.
Only semantic-release is marked self-hostable. automa is not.
automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
semantic-release scores 97.5 and automa scores 70.3. This page calls that a decisive lead for semantic-release.