A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 7.8 · clear
A · leads
99.1
95,849 stars · Apache-2.0
B
91.3
24,177 stars · MIT
puppeteer versus semantic-release 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; semantic-release is written mainly in JavaScript. The composite score is 99.1 for puppeteer and 91.3 for semantic-release.
puppeteer has 95,849 GitHub stars to semantic-release's 24,177, a gap of 71,672 (3.96×). Forks are 9,607 for puppeteer and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 82.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. semantic-release 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 semantic-release. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and semantic-release (24,177 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, semantic-release is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 18 points (100 vs 82), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against semantic-release at 91.3, a 7.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 | puppeteer | semantic-release |
|---|---|---|
| GitHub stars | 95,849 | 24,177 |
| Forks | 9,607 | 1,807 |
| Open issues | 201 | 410 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 91.3 |
JavaScript API for Chrome and Firefox
📦🚀 Fully automated version management and package publishing
puppeteer has more GitHub stars: 95,849 versus 24,177 for semantic-release. The gap is 71,672 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both puppeteer and semantic-release 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. semantic-release 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 semantic-release scores 91.3. This page calls that a clear lead for puppeteer.