A · level
archify
97.6
97,376 stars · Apache-2.0
AI Agents
Too close to call · 97.6 to 97.9
A · level
97.6
97,376 stars · Apache-2.0
B · level
97.9
108,897 stars · Apache-2.0
archify versus gemini-cli is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. archify is written mainly in JavaScript; gemini-cli is written mainly in TypeScript. The composite score is 97.6 for archify and 97.9 for gemini-cli.
gemini-cli has 108,897 GitHub stars to archify's 97,376, a gap of 11,521 (1.12×). Forks are 6,647 for archify and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 92 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 368 for archify (0.004 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both archify and gemini-cli are listed as Apache-2.0. 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 archify (97,376 stars) and gemini-cli (108,897 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: archify is open source, gemini-cli is open source.
The lead is split. archify is furthest ahead on issue health (96 to 84), while gemini-cli is furthest ahead on fork community (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: archify 97.6, gemini-cli 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | archify | gemini-cli |
|---|---|---|
| GitHub stars | 97,376 | 108,897 |
| Forks | 6,647 | 14,956 |
| Open issues | 368 | 739 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.6 | 97.9 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
An open-source AI agent that brings the power of Gemini directly into your terminal.
gemini-cli has more GitHub stars: 108,897 versus 97,376 for archify. The gap is 11,521 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both archify and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.
archify 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. gemini-cli 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.
Neither tool clears a one-point margin. archify scores 97.6 and gemini-cli scores 97.9.