Whitespace.
See who already built your idea — and the space they left open.

CLUSTER MAPS-CODE-DEPENDENCIES · 16 ENTRIES · EARLIEST ENTRY 2026-10-02

AI code dependency mapping tools

This cluster consists of tools that map code dependencies within a codebase and use AI to explain the resulting structure, often with interactive visualizations. The cluster's dated history is too thin to read a shape from, as only two dated entries predate the index start. VibeGraph and architecture-dissector lead on traction with 6 stars each, followed by compass with 2 stars.

Entry timeline

ENTRY TIMELINE

FEB 2026: 1MAY 2026: 1AUG 2026: 3SEP 2026: 4OCT 2026: 7
FEB 2026OCT 2026

Each bar is the month a member carries, which is a creation date where the source published one and a crawl date otherwise. Nothing in the index was found before 11 August 2026, and coverage broadened sharply on 14–15 August, so a bar from then on reports how much we found that month, not how much was built; an earlier bar reports how far back a member's own source dated it — not how long we have been watching.

Members by activity

Activity signals, not revenue.

Build origin · 2 ai-built · 14 unlabelled

Operator · 8 hobby · 1 indie · 7 unlabelled

Two labels per entry, never collapsed into one: how it was built, and who stands behind it. Counted over the 16 listed below. Unlabelled means nothing has decided yet — not that the answer is small.

  1. 01VibeGraph6★1 moliveai-builthobbyWeb application that parses uploaded codebases into interactive call graphs and generates AI explanations of functions and execution paths.
  2. 02architecture-dissector6★6 daysliveindieDesktop app that draws application architecture, workflows, and stored data from maps written by coding agents, and highlights what changed between versions.
  3. 03compass2★1 moliveBrowser-based dependency explorer that maps source files, imports, and architecture roles without uploading code.
  4. 04verilay2★9 days—ai-builtWeb app that analyzes AI-generated applications and produces plain-English maps of their components for non-developers.
  5. 05PlanProof1★21 dayslivehobbyWeb app that verifies AI-generated engineering plans against repository snapshots and returns evidence-based implementation plans before coding.
  6. 06CartoGraph1★7 days—hobbyWeb app that maps code dependency graphs in public repositories and uses AI to explain the resulting structure.
  7. 07strata0★6 dayslivemacOS app that visualizes a codebase as a zoomable map of code, architecture, and database, with an AI that reads the code alongside the user.
  8. 08Cartograph0★8 dayslivehobbyApp that reads a public GitHub repository and draws a dependency map, with AI explanations based only on parsed code.
  9. 09cartograph0★1 day—hobbyWeb app that analyzes codebases and maps dependencies with AI-powered visualizations for developers.
  10. 10x-ray0★17 days—hobbyLocal-first tool that turns any project folder into an interactive visual map of its structure, dependencies and impact, with optional AI explanations.
  11. 11mapo0★4 daysliveDesktop app that maps a codebase into an interactive visual map and shows dependencies and change impact for developers and AI agents.
  12. 12CodeGraph0★11 days—hobbyLocal app that visualizes dependency maps of public GitHub repositories and supports team workspaces.
  13. 13ZAtlas1★1 moliveDesktop app that maps codebases by drawing dependency graphs and highlighting dead code, import cycles, and churn for developers.
  14. 14ft_ai_learn0★1 mo—hobbyWeb app that presents an AI competency map as a navigable graph, unlocking nodes through Git-verified evidence and linking to study notebooks.
  15. 15Vast — AI-powered code architecture visualization0★unknownliveAn AI-powered code visualization tool that transforms microservice architectures into interactive dependency maps for developers.
  16. 16Godepgraph - A simple tool visualize Go package0★unknownliveWeb app that visualizes Go package dependencies to help developers understand project structure.

Ranked by traction, highest first, and paged 20 at a time — this is a window on the cluster, never the whole of it. Ties are broken by a stable id so a product cannot appear on two pages or fall between them. Browse every cluster.