A · leads
Scrapling
99.1
103,871 stars · BSD-3-Clause
Workflow Automation
Scrapling leads by 9.1 · clear
A · leads
99.1
103,871 stars · BSD-3-Clause
B
90.0
24,995 stars · GPL-3.0
Scrapling versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Scrapling is written mainly in Python; Tasmota is written mainly in C. The composite score is 99.1 for Scrapling and 90.0 for Tasmota.
Scrapling has 103,871 GitHub stars to Tasmota's 24,995, a gap of 78,876 (4.16×). Forks are 10,835 for Scrapling and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 92.
Push history: Scrapling was last pushed on 17 November 2026 (0 days ago), and Tasmota was last pushed on 17 November 2026 (0 days ago). Open issues stand at 21 for Scrapling (0.000 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 96 and 96; 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. Tasmota is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for Scrapling and 64 for Tasmota. This is a procurement signal, not legal advice.
In Workflow Automation, both Scrapling (103,871 stars) and Tasmota (24,995 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, Tasmota is open source.
Scrapling is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 32 points (96 vs 64), and the tightest is self-hosting at 0 points (100 vs 100).
Scrapling finishes ahead at 99.1 against Tasmota at 90.0, a 9.1 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 | Tasmota |
|---|---|---|
| GitHub stars | 103,871 | 24,995 |
| Forks | 10,835 | 5,216 |
| Open issues | 21 | 12 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 96 | 96 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 90.0 |
🕷️ 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
Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
Scrapling has more GitHub stars: 103,871 versus 24,995 for Tasmota. The gap is 78,876 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Scrapling and Tasmota 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. Tasmota is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Scrapling scores 99.1 and Tasmota scores 90.0. This page calls that a clear lead for Scrapling.