A
Obtainium
80.8
21,625 stars · GPL-3.0
Workflow Automation
puppeteer leads by 18.3 · decisive
A
80.8
21,625 stars · GPL-3.0
B · leads
99.1
95,849 stars · Apache-2.0
Obtainium versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Obtainium is written mainly in Dart; puppeteer is written mainly in TypeScript. The composite score is 80.8 for Obtainium and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to Obtainium's 21,625, a gap of 74,224 (4.43×). Forks are 704 for Obtainium and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 72 versus 100.
Push history: Obtainium was last pushed on 01 November 2026 (16 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 403 for Obtainium (0.019 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 78 and 100.
Obtainium 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. puppeteer 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. License scores in this pair are 64 for Obtainium and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both Obtainium (21,625 stars) and puppeteer (95,849 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: Obtainium is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against Obtainium at 80.8, a 18.3 point decisive 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 | Obtainium | puppeteer |
|---|---|---|
| GitHub stars | 21,625 | 95,849 |
| Forks | 704 | 9,607 |
| Open issues | 403 | 201 |
| Adoption | 87 | 100 |
| Activity | 78 | 100 |
| Community | 72 | 100 |
| Issue health | 84 | 96 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.8 | 99.1 |
Get Android app updates straight from the source.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 21,625 for Obtainium. The gap is 74,224 stars.
puppeteer was pushed more recently: 17 November 2026 versus 01 November 2026 for Obtainium. That is 16 days apart.
Yes. This catalog marks both Obtainium and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
Obtainium 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. puppeteer 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and Obtainium scores 80.8. This page calls that a decisive lead for puppeteer.