A · leads
ai-job-search
99.0
72,216 stars · MIT
AI Agents
ai-job-search leads by 6.4 · narrow
A · leads
99.0
72,216 stars · MIT
B
92.6
74,760 stars · MIT
ai-job-search 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. ai-job-search is written mainly in Python; Front-End-Checklist is written mainly in MDX. The composite score is 99.0 for ai-job-search and 92.6 for Front-End-Checklist.
Front-End-Checklist has 74,760 GitHub stars to ai-job-search's 72,216, a gap of 2,544 (1.04×). Forks are 23,222 for ai-job-search and 6,781 for Front-End-Checklist. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 88.
Push history: ai-job-search 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 72 for ai-job-search (0.001 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 ai-job-search 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 ai-job-search (72,216 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: ai-job-search is open source, Front-End-Checklist is open source.
The lead is split. ai-job-search is furthest ahead on recent activity (100 to 78), while Front-End-Checklist is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.
ai-job-search finishes ahead at 99.0 against Front-End-Checklist at 92.6, a 6.4 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-job-search | Front-End-Checklist |
|---|---|---|
| GitHub stars | 72,216 | 74,760 |
| Forks | 23,222 | 6,781 |
| Open issues | 72 | 22 |
| Adoption | 100 | 100 |
| Activity | 100 | 78 |
| Community | 100 | 88 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.0 | 92.6 |
The job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
🗂 The essential checklist for modern web development, for humans and AI agents
Front-End-Checklist has more GitHub stars: 74,760 versus 72,216 for ai-job-search. The gap is 2,544 stars.
ai-job-search 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 ai-job-search and Front-End-Checklist as self-hostable. Confirm each project's deploy docs before you plan a migration.
ai-job-search 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.
ai-job-search scores 99.0 and Front-End-Checklist scores 92.6. This page calls that a narrow lead for ai-job-search.