Skip to content
DevUtils Online

Workflow Automation

Airtest vs puppeteer

puppeteer leads by 28.1 · decisive

A

Airtest

71.0

9,655 stars · Apache-2.0

B · leads

puppeteer

99.1

95,849 stars · Apache-2.0

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

puppeteer has 95,849 GitHub stars to Airtest's 9,655, a gap of 86,194 (9.93×). Forks are 1,455 for Airtest and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 79 versus 100.

Push history: Airtest was last pushed on 23 March 2026 (239 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 486 for Airtest (0.050 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 52 and 96; activity scores are 36 and 100.

Both Airtest and puppeteer are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both Airtest (9,655 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: Airtest 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 Airtest at 71.0, a 28.1 point decisive 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.

Airtest versus puppeteer metrics
Signal Airtest puppeteer
GitHub stars 9,655 95,849
Forks 1,455 9,607
Open issues 486 201
Adoption 80 100
Activity 36 100
Community 79 100
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 71.0 99.1

Questions this page answers

Which has more GitHub stars, Airtest or puppeteer?

puppeteer has more GitHub stars: 95,849 versus 9,655 for Airtest. The gap is 86,194 stars.

Which was updated more recently, Airtest or puppeteer?

puppeteer was pushed more recently: 17 November 2026 versus 23 March 2026 for Airtest. That is 239 days apart.

Can I self-host both Airtest and puppeteer?

Yes. This catalog marks both Airtest 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, Airtest or puppeteer?

Airtest 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. 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 Airtest vs puppeteer score?

puppeteer scores 99.1 and Airtest scores 71.0. This page calls that a decisive lead for puppeteer.

Related comparisons