A · leads
appium
99.0
22,233 stars · Apache-2.0
Workflow Automation
appium leads by 8.0 · clear
A · leads
99.0
22,233 stars · Apache-2.0
B
91.0
23,434 stars · AGPL-3.0
appium versus skyvern 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; skyvern is written mainly in Python. The composite score is 99.0 for appium and 91.0 for skyvern.
skyvern has 23,434 GitHub stars to appium's 22,233, a gap of 1,201 (1.05×). Forks are 6,308 for appium and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 88.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for appium and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both appium (22,233 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. appium is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 99.0 against skyvern at 91.0, a 8.0 point clear 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 | skyvern |
|---|---|---|
| GitHub stars | 22,233 | 23,434 |
| Forks | 6,308 | 2,246 |
| Open issues | 40 | 301 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.0 | 91.0 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Automate browser based workflows with AI
skyvern has more GitHub stars: 23,434 versus 22,233 for appium. The gap is 1,201 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appium and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
appium scores 99.0 and skyvern scores 91.0. This page calls that a clear lead for appium.