A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 9.2 · clear
A · leads
99.1
95,849 stars · Apache-2.0
B
89.9
27,230 stars · MIT
puppeteer versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 99.1 for puppeteer and 89.9 for vagrant.
puppeteer has 95,849 GitHub stars to vagrant's 27,230, a gap of 68,619 (3.52×). Forks are 9,607 for puppeteer and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 92.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 96 and 70; activity scores are 100 and 92.
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. vagrant 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 vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and vagrant (27,230 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, vagrant 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 (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against vagrant at 89.9, a 9.2 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 | puppeteer | vagrant |
|---|---|---|
| GitHub stars | 95,849 | 27,230 |
| Forks | 9,607 | 4,491 |
| Open issues | 201 | 760 |
| Adoption | 100 | 89 |
| Activity | 100 | 92 |
| Community | 100 | 92 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 89.9 |
JavaScript API for Chrome and Firefox
Vagrant is a tool for building and distributing development environments.
puppeteer has more GitHub stars: 95,849 versus 27,230 for vagrant. The gap is 68,619 stars.
puppeteer was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both puppeteer and vagrant 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. vagrant 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 99.1 and vagrant scores 89.9. This page calls that a clear lead for puppeteer.