A · leads
puppeteer
98.4
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 16.5 · decisive
A · leads
98.4
95,849 stars · Apache-2.0
B
81.9
9,647 stars · MIT
puppeteer versus TitanBot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. puppeteer is written mainly in TypeScript; TitanBot is written mainly in JavaScript. The composite score is 98.4 for puppeteer and 81.9 for TitanBot.
puppeteer has 95,849 GitHub stars to TitanBot's 9,647, a gap of 86,202 (9.94×). Forks are 9,607 for puppeteer and 15,304 for TitanBot. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 95 versus 100.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and TitanBot was last pushed on 03 September 2026 (75 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 85 for TitanBot (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 58.
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. TitanBot 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. License scores in this pair are 96 for puppeteer and 96 for TitanBot. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and TitanBot (9,647 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: puppeteer is open source, TitanBot is open source.
The lead is split. puppeteer is furthest ahead on recent activity (100 to 58), while TitanBot is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
puppeteer finishes ahead at 98.4 against TitanBot at 81.9, a 16.5 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 | puppeteer | TitanBot |
|---|---|---|
| GitHub stars | 95,849 | 9,647 |
| Forks | 9,607 | 15,304 |
| Open issues | 201 | 85 |
| Adoption | 100 | 80 |
| Activity | 100 | 58 |
| Community | 95 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.4 | 81.9 |
JavaScript API for Chrome and Firefox
A powerful, all-in-one Discord assistant built for every server.
puppeteer has more GitHub stars: 95,849 versus 9,647 for TitanBot. The gap is 86,202 stars.
puppeteer was pushed more recently: 17 November 2026 versus 03 September 2026 for TitanBot. That is 75 days apart.
Yes. This catalog marks both puppeteer and TitanBot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. TitanBot 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 98.4 and TitanBot scores 81.9. This page calls that a decisive lead for puppeteer.