A
MobileAgent
84.3
9,385 stars · MIT
Workflow Automation
puppeteer leads by 14.8 · clear
A
84.3
9,385 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
MobileAgent versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. MobileAgent is written mainly in Python; puppeteer is written mainly in TypeScript. The composite score is 84.3 for MobileAgent and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to MobileAgent's 9,385, a gap of 86,464 (10.21×). Forks are 946 for MobileAgent and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 75 versus 100.
Push history: MobileAgent was last pushed on 03 November 2026 (14 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 197 for MobileAgent (0.021 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 92 and 100.
MobileAgent 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. 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 96 for MobileAgent and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both MobileAgent (9,385 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: MobileAgent is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: 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).
puppeteer finishes ahead at 99.1 against MobileAgent at 84.3, a 14.8 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 | MobileAgent | puppeteer |
|---|---|---|
| GitHub stars | 9,385 | 95,849 |
| Forks | 946 | 9,607 |
| Open issues | 197 | 201 |
| Adoption | 80 | 100 |
| Activity | 92 | 100 |
| Community | 75 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.3 | 99.1 |
Mobile-Agent: The Powerful GUI Agent Family
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 9,385 for MobileAgent. The gap is 86,464 stars.
puppeteer was pushed more recently: 17 November 2026 versus 03 November 2026 for MobileAgent. That is 14 days apart.
Yes. This catalog marks both MobileAgent and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
MobileAgent 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. 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 MobileAgent scores 84.3. This page calls that a clear lead for puppeteer.