A
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
puppeteer leads by 1.2 · narrow
A
97.4
112,653 stars · MIT
B · leads
98.6
95,849 stars · Apache-2.0
Agent-Reach versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Agent-Reach is written mainly in Python; puppeteer is written mainly in TypeScript. The composite score is 97.4 for Agent-Reach and 98.6 for puppeteer.
Agent-Reach has 112,653 GitHub stars to puppeteer's 95,849, a gap of 16,804 (1.18×). Forks are 10,094 for Agent-Reach and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 100.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
Agent-Reach 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 Agent-Reach and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 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: Agent-Reach is open source, puppeteer is open source.
The lead is split. Agent-Reach is furthest ahead on adoption (100 to 99), while puppeteer is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
puppeteer finishes ahead at 98.6 against Agent-Reach at 97.4, a 1.2 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 | Agent-Reach | puppeteer |
|---|---|---|
| GitHub stars | 112,653 | 95,849 |
| Forks | 10,094 | 9,607 |
| Open issues | 133 | 201 |
| Adoption | 100 | 99 |
| Activity | 92 | 100 |
| Community | 100 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 98.6 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
JavaScript API for Chrome and Firefox
Agent-Reach has more GitHub stars: 112,653 versus 95,849 for puppeteer. The gap is 16,804 stars.
puppeteer was pushed more recently: 17 November 2026 versus 08 November 2026 for Agent-Reach. That is 9 days apart.
Yes. This catalog marks both Agent-Reach and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
Agent-Reach 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 98.6 and Agent-Reach scores 97.4. This page calls that a narrow lead for puppeteer.