Skip to content
DevUtils Online

Workflow Automation

semantic-release vs vagrant

semantic-release leads by 1.2 · narrow

B

vagrant

94.8

27,230 stars · MIT

semantic-release versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. semantic-release is written mainly in JavaScript; vagrant is written mainly in Ruby. The composite score is 96.0 for semantic-release and 94.8 for vagrant.

vagrant has 27,230 GitHub stars to semantic-release's 24,177, a gap of 3,053 (1.13×). Forks are 1,807 for semantic-release and 4,491 for vagrant. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 89 versus 100.

Push history: semantic-release was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 410 for semantic-release (0.017 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.

Both semantic-release and vagrant 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 semantic-release (24,177 stars) and vagrant (27,230 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: semantic-release is open source, vagrant is open source.

The lead is split. semantic-release is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 89). Choose the dimension a rollout cannot compromise on.

semantic-release finishes ahead at 96.0 against vagrant at 94.8, a 1.2 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

semantic-release versus vagrant metrics
Signal semantic-release vagrant
GitHub stars 24,177 27,230
Forks 1,807 4,491
Open issues 410 760
Adoption 99 100
Activity 100 92
Community 89 100
Issue health 84 70
License 96 96
Self-hosting 100 100
Composite 96.0 94.8

Questions this page answers

Which has more GitHub stars, semantic-release or vagrant?

vagrant has more GitHub stars: 27,230 versus 24,177 for semantic-release. The gap is 3,053 stars.

Which was updated more recently, semantic-release or vagrant?

semantic-release was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.

Can I self-host both semantic-release and vagrant?

Yes. This catalog marks both semantic-release and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, semantic-release or vagrant?

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. vagrant 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.

Who wins the semantic-release vs vagrant score?

semantic-release scores 96.0 and vagrant scores 94.8. This page calls that a narrow lead for semantic-release.

Related comparisons