A
Front-End-Checklist
88.1
74,760 stars · MIT
AI Agents
hermes-agent leads by 4.8 · narrow
A
88.1
74,760 stars · MIT
B · leads
92.9
264,096 stars · MIT
Front-End-Checklist versus hermes-agent 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; hermes-agent is written mainly in Python. The composite score is 88.1 for Front-End-Checklist and 92.9 for hermes-agent.
hermes-agent has 264,096 GitHub stars to Front-End-Checklist's 74,760, a gap of 189,336 (3.53×). Forks are 6,781 for Front-End-Checklist and 59,569 for hermes-agent. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 80 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and hermes-agent was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 53,403 for hermes-agent (0.202 per star). Issue-health scores are 96 and 34; activity scores are 78 and 100.
Both Front-End-Checklist and hermes-agent 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 Front-End-Checklist (74,760 stars) and hermes-agent (264,096 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, hermes-agent is open source.
The lead is split. Front-End-Checklist is furthest ahead on issue health (96 to 34), while hermes-agent is furthest ahead on recent activity (100 to 78). Choose the dimension a rollout cannot compromise on.
hermes-agent finishes ahead at 92.9 against Front-End-Checklist at 88.1, a 4.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 | Front-End-Checklist | hermes-agent |
|---|---|---|
| GitHub stars | 74,760 | 264,096 |
| Forks | 6,781 | 59,569 |
| Open issues | 22 | 53,403 |
| Adoption | 90 | 100 |
| Activity | 78 | 100 |
| Community | 80 | 100 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.1 | 92.9 |
🗂 The essential checklist for modern web development, for humans and AI agents
The agent that grows with you
hermes-agent has more GitHub stars: 264,096 versus 74,760 for Front-End-Checklist. The gap is 189,336 stars.
hermes-agent 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 hermes-agent 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. hermes-agent 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.
hermes-agent scores 92.9 and Front-End-Checklist scores 88.1. This page calls that a narrow lead for hermes-agent.