A
hammerspoon
73.3
16,443 stars · MIT
Workflow Automation
puppeteer leads by 25.8 · decisive
A
73.3
16,443 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
hammerspoon versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. hammerspoon is written mainly in Objective-C; puppeteer is written mainly in TypeScript. The composite score is 73.3 for hammerspoon and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to hammerspoon's 16,443, a gap of 79,406 (5.83×). Forks are 738 for hammerspoon and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 72 versus 100.
Push history: hammerspoon was last pushed on 08 July 2026 (131 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for hammerspoon (0.043 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 36 and 100.
hammerspoon 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 hammerspoon and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both hammerspoon (16,443 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: hammerspoon 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 recent activity at 64 points (36 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against hammerspoon at 73.3, a 25.8 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 | hammerspoon | puppeteer |
|---|---|---|
| GitHub stars | 16,443 | 95,849 |
| Forks | 738 | 9,607 |
| Open issues | 708 | 201 |
| Adoption | 85 | 100 |
| Activity | 36 | 100 |
| Community | 72 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 73.3 | 99.1 |
Staggeringly powerful macOS desktop automation with Lua
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 16,443 for hammerspoon. The gap is 79,406 stars.
puppeteer was pushed more recently: 17 November 2026 versus 08 July 2026 for hammerspoon. That is 131 days apart.
Yes. This catalog marks both hammerspoon and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
hammerspoon 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 hammerspoon scores 73.3. This page calls that a decisive lead for puppeteer.