A · leads
Scrapling
99.1
103,871 stars · BSD-3-Clause
Workflow Automation
Scrapling leads by 13.2 · clear
A · leads
99.1
103,871 stars · BSD-3-Clause
B
85.9
23,434 stars · AGPL-3.0
Scrapling versus skyvern 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 Python. The composite score is 99.1 for Scrapling and 85.9 for skyvern.
Scrapling has 103,871 GitHub stars to skyvern's 23,434, a gap of 80,437 (4.43×). Forks are 10,835 for Scrapling and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 83.
Push history: Scrapling 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 21 for Scrapling (0.000 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Scrapling is listed as BSD-3-Clause, 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 Scrapling and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both Scrapling (103,871 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: Scrapling is open source, skyvern is open source.
Scrapling is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Scrapling finishes ahead at 99.1 against skyvern at 85.9, a 13.2 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 | Scrapling | skyvern |
|---|---|---|
| GitHub stars | 103,871 | 23,434 |
| Forks | 10,835 | 2,246 |
| Open issues | 21 | 301 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 85.9 |
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Automate browser based workflows with AI
Scrapling has more GitHub stars: 103,871 versus 23,434 for skyvern. The gap is 80,437 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Scrapling and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.
Scrapling is listed as BSD-3-Clause, 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.
Scrapling scores 99.1 and skyvern scores 85.9. This page calls that a clear lead for Scrapling.