A · leads
deepseek-harness
97.4
282,805 stars · MIT
AI Agents
deepseek-harness leads by 2.4 · narrow
A · leads
97.4
282,805 stars · MIT
B
95.0
149,362 stars · Apache-2.0
deepseek-harness versus graphify is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. deepseek-harness is written mainly in TypeScript; graphify is written mainly in Python. The composite score is 97.4 for deepseek-harness and 95.0 for graphify.
deepseek-harness has 282,805 GitHub stars to graphify's 149,362, a gap of 133,443 (1.89×). Forks are 35,041 for deepseek-harness and 14,362 for graphify. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 92.
Push history: deepseek-harness was last pushed on 13 November 2026 (4 days ago), and graphify was last pushed on 16 November 2026 (1 day ago). Open issues stand at 0 for deepseek-harness (0.000 per star) and 1,670 for graphify (0.011 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
deepseek-harness 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. graphify 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 deepseek-harness and 96 for graphify. This is a procurement signal, not legal advice.
In AI Agents, both deepseek-harness (282,805 stars) and graphify (149,362 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: deepseek-harness is open source, graphify is open source.
The lead is split. deepseek-harness is furthest ahead on issue health (96 to 84), while graphify is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
deepseek-harness finishes ahead at 97.4 against graphify at 95.0, a 2.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 | deepseek-harness | graphify |
|---|---|---|
| GitHub stars | 282,805 | 149,362 |
| Forks | 35,041 | 14,362 |
| Open issues | 0 | 1,670 |
| Adoption | 100 | 95 |
| Activity | 92 | 100 |
| Community | 100 | 92 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 95.0 |
DeepSeek Harness: Everything is a Plugin.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
deepseek-harness has more GitHub stars: 282,805 versus 149,362 for graphify. The gap is 133,443 stars.
graphify was pushed more recently: 16 November 2026 versus 13 November 2026 for deepseek-harness. That is 3 days apart.
Yes. This catalog marks both deepseek-harness and graphify as self-hostable. Confirm each project's deploy docs before you plan a migration.
deepseek-harness 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. graphify 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.
deepseek-harness scores 97.4 and graphify scores 95.0. This page calls that a narrow lead for deepseek-harness.