A
bruno
92.4
48,427 stars · MIT
Workflow Automation
Scrapling leads by 6.7 · narrow
A
92.4
48,427 stars · MIT
B · leads
99.1
103,871 stars · BSD-3-Clause
bruno versus Scrapling is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; Scrapling is written mainly in Python. The composite score is 92.4 for bruno and 99.1 for Scrapling.
Scrapling has 103,871 GitHub stars to bruno's 48,427, a gap of 55,444 (2.14×). Forks are 3,115 for bruno and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 87 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 21 for Scrapling (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
bruno 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. 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. License scores in this pair are 96 for bruno and 96 for Scrapling. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and Scrapling (103,871 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: bruno is open source, Scrapling is open source.
Scrapling is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (70 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Scrapling finishes ahead at 99.1 against bruno at 92.4, a 6.7 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 | bruno | Scrapling |
|---|---|---|
| GitHub stars | 48,427 | 103,871 |
| Forks | 3,115 | 10,835 |
| Open issues | 2,002 | 21 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.4 | 99.1 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
🕷️ 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
Scrapling has more GitHub stars: 103,871 versus 48,427 for bruno. The gap is 55,444 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and Scrapling as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Scrapling scores 99.1 and bruno scores 92.4. This page calls that a narrow lead for Scrapling.