A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 11.6 · clear
A · leads
97.4
112,653 stars · MIT
B
85.8
23,434 stars · AGPL-3.0
Agent-Reach versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.4 for Agent-Reach and 85.8 for skyvern.
Agent-Reach has 112,653 GitHub stars to skyvern's 23,434, a gap of 89,219 (4.81×). Forks are 10,094 for Agent-Reach and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 84.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Agent-Reach and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. Agent-Reach is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Agent-Reach finishes ahead at 97.4 against skyvern at 85.8, a 11.6 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 | Agent-Reach | skyvern |
|---|---|---|
| GitHub stars | 112,653 | 23,434 |
| Forks | 10,094 | 2,246 |
| Open issues | 133 | 301 |
| Adoption | 100 | 86 |
| Activity | 92 | 100 |
| Community | 100 | 84 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 85.8 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Automate browser based workflows with AI
Agent-Reach has more GitHub stars: 112,653 versus 23,434 for skyvern. The gap is 89,219 stars.
skyvern 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 skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Agent-Reach scores 97.4 and skyvern scores 85.8. This page calls that a clear lead for Agent-Reach.