Head to head
Latchkey vs Github Repo
Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.
No reviews yet
Triage failing GitHub Actions jobs and see what self-heal repaired, in natural language.
Full listing
No reviews yet
MCP server for GitHub repo health, commit summaries, issue triage, and RAG Q&A.
Full listingThe short version
Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours Github Repo (83/100 against 57). Latchkey is hosted and callable through the gateway; Github Repo runs on your own machine. Github Repo has noticeably more public adoption.
| Latchkey | Github Repo | |
|---|---|---|
| User rating | No reviews yet | No reviews yet |
| Safety grade | C57/100 | B83/100 |
| Adoption | New | Growing |
| GitHub stars | – | 1 |
| Downloads / week | – | 150 |
| Runs where | Hosted (remote) | Your machine (local) |
| Gateway-ready | Yes | No |
| Tools | — | 4 |
| Write actions | — | — |
| Price per call | Free | Free |
| Licence | — | MIT |
| Last release | — | 2026-09-16 |
| Category | Developer tools | Developer tools |