A
Front-End-Checklist
93.6
74,760 stars · MIT
AI Agents
hyperframes leads by 5.5 · narrow
A
93.6
74,760 stars · MIT
B · leads
99.1
85,709 stars · Apache-2.0
Front-End-Checklist versus hyperframes 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; hyperframes is written mainly in TypeScript. The composite score is 93.6 for Front-End-Checklist and 99.1 for hyperframes.
hyperframes has 85,709 GitHub stars to Front-End-Checklist's 74,760, a gap of 10,949 (1.15×). Forks are 6,781 for Front-End-Checklist and 7,946 for hyperframes. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 98 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and hyperframes was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 293 for hyperframes (0.003 per star). Issue-health scores are 96 and 96; 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. hyperframes 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 hyperframes. This is a procurement signal, not legal advice.
In AI Agents, both Front-End-Checklist (74,760 stars) and hyperframes (85,709 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, hyperframes is open source.
hyperframes 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 (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
hyperframes finishes ahead at 99.1 against Front-End-Checklist at 93.6, a 5.5 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 | hyperframes |
|---|---|---|
| GitHub stars | 74,760 | 85,709 |
| Forks | 6,781 | 7,946 |
| Open issues | 22 | 293 |
| Adoption | 99 | 100 |
| Activity | 78 | 100 |
| Community | 98 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.6 | 99.1 |
🗂 The essential checklist for modern web development, for humans and AI agents
Write HTML. Render video. Built for agents.
hyperframes has more GitHub stars: 85,709 versus 74,760 for Front-End-Checklist. The gap is 10,949 stars.
hyperframes 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 hyperframes 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. hyperframes 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.
hyperframes scores 99.1 and Front-End-Checklist scores 93.6. This page calls that a narrow lead for hyperframes.