codeflow vs ontology-atlas
Paste a GitHub URL or drop a local folder → interactive architecture map in the browser: dependency graph, blast radius, health grade, security scan. Single index.html, zero install. — versus — Desktop app plus MCP server keeping a codebase's ontology as reviewable Markdown in the repo: domains and capabilities linked to code evidence, compiled to a graph for blast-radius queries.
Both produce a navigable architecture map of a repo. Codeflow derives one in the browser from a URL in minutes with zero upkeep; Atlas makes you write and review it, trading effort for an explanation the parser can't infer.
| codeflow | ontology-atlas | |
|---|---|---|
| Stars | 5.1k | 85 |
| Forks | 758 | 14 |
| Language | HTML | TypeScript |
| License | MIT | MIT |
| Last activity | yesterday | today |
| Topics | code-intel | knowledge-graphs, code-intel, coding |
| Curated connections | 4 | 5 |
codeflow — the curator's take
The fastest 'what am I looking at?' tool for an unfamiliar repo: zero install, code never leaves the browser, and blast-radius answers 'what breaks if I touch this?' before you refactor. The JSON export and README-card GitHub Action make it more than a toy. NOT compiler-grade: dependency edges come from lightweight in-browser parsing across 30+ languages, so trust it for orientation, not for exhaustive call-graph truth — agents needing tree-sitter-accurate graphs should use code-review-graph or codegraph-mcp. Big repos also eat GitHub API rate limits fast without a token.
ontology-atlas — the curator's take
Pick it when the expensive question is *why* the code is shaped this way and what a change will touch. Because the ontology is authored and reviewed rather than inferred, unknown coverage shows up as unknown instead of a confident wrong graph — and every agent write lands as a diffable line in a Markdown file. It is not a code indexer: it will not find symbols or callers, and it only knows what someone wrote down, so an unmaintained atlas/ rots quietly while still looking authoritative. Practical caveat: this is a desktop install with an unsigned Windows beta; Linux and CI users run the CLI and MCP server from source.