A
Huginn
93.1
50,561 stars · MIT
Workflow Automation
puppeteer leads by 6.0 · narrow
A
93.1
50,561 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
Huginn versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Huginn is written mainly in Ruby; puppeteer is written mainly in TypeScript. The composite score is 93.1 for Huginn and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to Huginn's 50,561, a gap of 45,288 (1.90×). Forks are 4,356 for Huginn and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 91 versus 100.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 92 and 100.
Huginn 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 Huginn and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 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: Huginn 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 issue health at 12 points (84 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against Huginn at 93.1, a 6.0 point narrow 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 | Huginn | puppeteer |
|---|---|---|
| GitHub stars | 50,561 | 95,849 |
| Forks | 4,356 | 9,607 |
| Open issues | 692 | 201 |
| Adoption | 94 | 100 |
| Activity | 92 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.1 | 99.1 |
Huginn is a self-hosted agent system that watches the web and triggers actions from events. It predates the current wave of LLM agents and is closer to a personal IFTTT you run yourself.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 50,561 for Huginn. The gap is 45,288 stars.
puppeteer was pushed more recently: 17 November 2026 versus 09 November 2026 for Huginn. That is 8 days apart.
Yes. This catalog marks both Huginn and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
Huginn 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 Huginn scores 93.1. This page calls that a narrow lead for puppeteer.