A · leads
graphify
97.9
149,362 stars · Apache-2.0
AI Agents
graphify leads by 1.2 · narrow
A · leads
97.9
149,362 stars · Apache-2.0
B
96.7
85,709 stars · Apache-2.0
graphify versus hyperframes is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. graphify is written mainly in Python; hyperframes is written mainly in TypeScript. The composite score is 97.9 for graphify and 96.7 for hyperframes.
graphify has 149,362 GitHub stars to hyperframes's 85,709, a gap of 63,653 (1.74×). Forks are 14,362 for graphify and 7,946 for hyperframes. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 94.
Push history: graphify was last pushed on 16 November 2026 (1 day ago), and hyperframes was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,670 for graphify (0.011 per star) and 293 for hyperframes (0.003 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both graphify and hyperframes 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 graphify (149,362 stars) and hyperframes (85,709 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: graphify is open source, hyperframes is open source.
The lead is split. graphify is furthest ahead on fork community (100 to 94), while hyperframes is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
graphify finishes ahead at 97.9 against hyperframes at 96.7, a 1.2 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 | graphify | hyperframes |
|---|---|---|
| GitHub stars | 149,362 | 85,709 |
| Forks | 14,362 | 7,946 |
| Open issues | 1,670 | 293 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 96.7 |
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.
Write HTML. Render video. Built for agents.
graphify has more GitHub stars: 149,362 versus 85,709 for hyperframes. The gap is 63,653 stars.
hyperframes was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both graphify and hyperframes as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. hyperframes 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.
graphify scores 97.9 and hyperframes scores 96.7. This page calls that a narrow lead for graphify.