A · leads
appium
98.4
22,233 stars · Apache-2.0
Workflow Automation
appium leads by 4.2 · narrow
A · leads
98.4
22,233 stars · Apache-2.0
B
94.2
27,230 stars · MIT
appium versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. appium is written mainly in TypeScript; vagrant is written mainly in Ruby. The composite score is 98.4 for appium and 94.2 for vagrant.
vagrant has 27,230 GitHub stars to appium's 22,233, a gap of 4,997 (1.22×). Forks are 6,308 for appium and 4,491 for vagrant. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 96.
Push history: appium 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 40 for appium (0.002 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 96 and 70; activity scores are 100 and 92.
appium 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. 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. License scores in this pair are 96 for appium and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both appium (22,233 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: appium is open source, vagrant is open source.
The lead is split. appium is furthest ahead on issue health (96 to 70), while vagrant is furthest ahead on adoption (100 to 98). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 98.4 against vagrant at 94.2, a 4.2 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 | appium | vagrant |
|---|---|---|
| GitHub stars | 22,233 | 27,230 |
| Forks | 6,308 | 4,491 |
| Open issues | 40 | 760 |
| Adoption | 98 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 96 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.4 | 94.2 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 22,233 for appium. The gap is 4,997 stars.
appium was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both appium and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
appium 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. 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.
appium scores 98.4 and vagrant scores 94.2. This page calls that a narrow lead for appium.