A · leads
browser-use
99.1
121,292 stars · MIT
AI Agents
browser-use leads by 7.2 · clear
A · leads
99.1
121,292 stars · MIT
B
91.9
74,760 stars · MIT
browser-use versus Front-End-Checklist is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. browser-use is written mainly in Python; Front-End-Checklist is written mainly in MDX. The composite score is 99.1 for browser-use and 91.9 for Front-End-Checklist.
browser-use has 121,292 GitHub stars to Front-End-Checklist's 74,760, a gap of 46,532 (1.62×). Forks are 13,561 for browser-use and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 93.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and Front-End-Checklist was last pushed on 31 October 2026 (17 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 22 for Front-End-Checklist (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 78.
Both browser-use and Front-End-Checklist are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both browser-use (121,292 stars) and Front-End-Checklist (74,760 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: browser-use is open source, Front-End-Checklist is open source.
browser-use is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
browser-use finishes ahead at 99.1 against Front-End-Checklist at 91.9, a 7.2 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 | browser-use | Front-End-Checklist |
|---|---|---|
| GitHub stars | 121,292 | 74,760 |
| Forks | 13,561 | 6,781 |
| Open issues | 596 | 22 |
| Adoption | 100 | 96 |
| Activity | 100 | 78 |
| Community | 100 | 93 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 91.9 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
🗂 The essential checklist for modern web development, for humans and AI agents
browser-use has more GitHub stars: 121,292 versus 74,760 for Front-End-Checklist. The gap is 46,532 stars.
browser-use was pushed more recently: 17 November 2026 versus 31 October 2026 for Front-End-Checklist. That is 17 days apart.
Yes. This catalog marks both browser-use and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
browser-use 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. Front-End-Checklist 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.
browser-use scores 99.1 and Front-End-Checklist scores 91.9. This page calls that a clear lead for browser-use.