Skip to content
DevUtils Online

Workflow Automation

AutoHotkey vs puppeteer

puppeteer leads by 12.8 · clear

B · leads

puppeteer

99.1

95,849 stars · Apache-2.0

AutoHotkey versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. AutoHotkey is written mainly in C++; puppeteer is written mainly in TypeScript. The composite score is 86.3 for AutoHotkey and 99.1 for puppeteer.

puppeteer has 95,849 GitHub stars to AutoHotkey's 13,492, a gap of 82,357 (7.10×). Forks are 1,206 for AutoHotkey and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 77 versus 100.

Push history: AutoHotkey was last pushed on 13 November 2026 (3 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 13 for AutoHotkey (0.001 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.

AutoHotkey is listed as GPL-2.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 AutoHotkey and 96 for puppeteer. This is a procurement signal, not legal advice.

In Workflow Automation, both AutoHotkey (13,492 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: AutoHotkey is open source, puppeteer is open source.

puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, 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 AutoHotkey at 86.3, a 12.8 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

AutoHotkey versus puppeteer metrics
Signal AutoHotkey puppeteer
GitHub stars 13,492 95,849
Forks 1,206 9,607
Open issues 13 201
Adoption 83 100
Activity 100 100
Community 77 100
Issue health 96 96
License 64 96
Self-hosting 100 100
Composite 86.3 99.1

Questions this page answers

Which has more GitHub stars, AutoHotkey or puppeteer?

puppeteer has more GitHub stars: 95,849 versus 13,492 for AutoHotkey. The gap is 82,357 stars.

Which was updated more recently, AutoHotkey or puppeteer?

puppeteer was pushed more recently: 17 November 2026 versus 13 November 2026 for AutoHotkey. That is 3 days apart.

Can I self-host both AutoHotkey and puppeteer?

Yes. This catalog marks both AutoHotkey and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, AutoHotkey or puppeteer?

AutoHotkey is listed as GPL-2.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.

Who wins the AutoHotkey vs puppeteer score?

puppeteer scores 99.1 and AutoHotkey scores 86.3. This page calls that a clear lead for puppeteer.

Related comparisons