A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 1.7 · narrow
A · leads
96.5
48,427 stars · MIT
B
94.8
24,177 stars · MIT
bruno 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 96.5 for bruno and 94.8 for semantic-release.
bruno has 48,427 GitHub stars to semantic-release's 24,177, a gap of 24,250 (2.00×). Forks are 3,115 for bruno 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 93.
Push history: bruno 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 2,002 for bruno (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.
Both bruno and semantic-release are listed as MIT. 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 bruno (48,427 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: bruno is open source, semantic-release is open source.
The lead is split. bruno is furthest ahead on fork community (100 to 93), while semantic-release is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
bruno finishes ahead at 96.5 against semantic-release at 94.8, a 1.7 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 | bruno | semantic-release |
|---|---|---|
| GitHub stars | 48,427 | 24,177 |
| Forks | 3,115 | 1,807 |
| Open issues | 2,002 | 410 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 94.8 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
📦🚀 Fully automated version management and package publishing
bruno has more GitHub stars: 48,427 versus 24,177 for semantic-release. The gap is 24,250 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and semantic-release as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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. 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.
bruno scores 96.5 and semantic-release scores 94.8. This page calls that a narrow lead for bruno.