A · leads
ai-goofish-monitor
93.8
20,135 stars · MIT
Workflow Automation
ai-goofish-monitor leads by 1.8 · narrow
A · leads
93.8
20,135 stars · MIT
B
92.0
23,434 stars · AGPL-3.0
ai-goofish-monitor 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 93.8 for ai-goofish-monitor and 92.0 for skyvern.
skyvern has 23,434 GitHub stars to ai-goofish-monitor's 20,135, a gap of 3,299 (1.16×). Forks are 3,258 for ai-goofish-monitor and 2,246 for skyvern. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 95.
Push history: ai-goofish-monitor was last pushed on 10 October 2026 (38 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 66 for ai-goofish-monitor (0.003 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; activity scores are 78 and 100.
ai-goofish-monitor 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 ai-goofish-monitor and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both ai-goofish-monitor (20,135 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: ai-goofish-monitor is open source, skyvern is open source.
The lead is split. ai-goofish-monitor is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
ai-goofish-monitor finishes ahead at 93.8 against skyvern at 92.0, a 1.8 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 | ai-goofish-monitor | skyvern |
|---|---|---|
| GitHub stars | 20,135 | 23,434 |
| Forks | 3,258 | 2,246 |
| Open issues | 66 | 301 |
| Adoption | 98 | 100 |
| Activity | 78 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.8 | 92.0 |
基于 Playwright 和AI实现的闲鱼多任务实时/定时监控与智能分析系统,配备了功能完善的后台管理UI。帮助用户从闲鱼海量商品中,找到心仪产品。
Automate browser based workflows with AI
skyvern has more GitHub stars: 23,434 versus 20,135 for ai-goofish-monitor. The gap is 3,299 stars.
skyvern was pushed more recently: 17 November 2026 versus 10 October 2026 for ai-goofish-monitor. That is 38 days apart.
Yes. This catalog marks both ai-goofish-monitor and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.
ai-goofish-monitor 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.
ai-goofish-monitor scores 93.8 and skyvern scores 92.0. This page calls that a narrow lead for ai-goofish-monitor.