BlastRadius

Explore any big repository in minutes. Third place at the hackathon.

Year: 2026
Role: Hackathon team · 3rd place
Stack: TypeScript, tree-sitter, D3, VS Code API
Links: Repository ↗

Blast Radius function call graph mapping 586 functions with a selected function's callers and risk details

Overview

Blast Radius helps new developers understand big repositories quickly. It maps out an entire codebase, every function and every call between them, and shows how far a change to any function would reach.

We built it at a hackathon, where it won third place. Beyond the call graph, it packs a whole suite of tools into one place: a DevOps view that maps your services, ports and volumes, a database schema explorer, Git history and backups, a function index and an AI context export.

The idea is simple, but the execution is what made it stand out, especially the retro, game-inspired interface, which makes exploring a huge codebase feel more like playing than reading.

3rdPlace at the hackathon

586Functions mapped in the demo repo

9Tools in one interface

What we built

01
A function call graph that maps every function in a repository and highlights how far a change to any one of them reaches.
02
A DevOps view that turns your Docker setup into a diagram of services, ports, volumes and dependencies, with automatic checks for common mistakes.
03
A database schema explorer that detects tables and relationships from migrations and lays them out automatically.
04
Git history and backups, a searchable function index and an AI context export, all in the same interface.

Gallery

Blast Radius function call graph with a function index and risk details for the selected function — Function call graph and index

Blast Radius DevOps view showing web, API, Postgres and Redis services with configuration checks — DevOps view with service checks

Blast Radius database schema explorer with tables and relationships arranged automatically — Database schema explorer

Challenges

The obvious one was time. We had a single hackathon to go from an idea to a working tool, and we kept adding features: the call graph, the DevOps view, the schema explorer, Git backups and more.

Shipping that much in so little time meant ruthless prioritisation. Each feature had to be simple enough to finish, and the interface had to make all of it feel like one product rather than a pile of tabs.