A
Front-End-Checklist
94.3
74,760 stars · MIT
AI Agents
goose leads by 2.7 · narrow
A
94.3
74,760 stars · MIT
B · leads
97.0
56,716 stars · Apache-2.0
Front-End-Checklist versus goose is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Front-End-Checklist is written mainly in MDX; goose is written mainly in Rust. The composite score is 94.3 for Front-End-Checklist and 97.0 for goose.
Front-End-Checklist has 74,760 GitHub stars to goose's 56,716, a gap of 18,044 (1.32×). Forks are 6,781 for Front-End-Checklist and 6,608 for goose. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and goose was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 530 for goose (0.009 per star). Issue-health scores are 96 and 84; activity scores are 78 and 100.
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. goose 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 Front-End-Checklist and 96 for goose. This is a procurement signal, not legal advice.
In AI Agents, both Front-End-Checklist (74,760 stars) and goose (56,716 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: Front-End-Checklist is open source, goose is open source.
The lead is split. Front-End-Checklist is furthest ahead on issue health (96 to 84), while goose is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
goose finishes ahead at 97.0 against Front-End-Checklist at 94.3, a 2.7 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 | Front-End-Checklist | goose |
|---|---|---|
| GitHub stars | 74,760 | 56,716 |
| Forks | 6,781 | 6,608 |
| Open issues | 22 | 530 |
| Adoption | 100 | 98 |
| Activity | 78 | 100 |
| Community | 100 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.3 | 97.0 |
🗂 The essential checklist for modern web development, for humans and AI agents
an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
Front-End-Checklist has more GitHub stars: 74,760 versus 56,716 for goose. The gap is 18,044 stars.
goose 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 Front-End-Checklist and goose as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. goose 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.
goose scores 97.0 and Front-End-Checklist scores 94.3. This page calls that a narrow lead for goose.