repowiserepowise

App

dundee / gdu

Fast disk usage analyzer with console interface written in Go

★ 6,203stars on GitHubGoMIT

This connects Repowise to dundee/gdu's code. It does not install gdu.

Repowise maps public repos from their source. Not affiliated with dundee. What is Repowise?

github.com/dundee/gduIndexed at 02225e4

What is gdu?

gdu is a console disk usage analyzer for finding out how much space directories and files take up. It scans a directory tree and reports the sizes in an interactive terminal view, or as plain statistics or JSON when its output is redirected. The project is written in Go. Its code health is 6.8 out of 10 (Fair), ranked #155 of 4,000+ indexed repos. The last commit to gdu was on Jun 2, 2026.

As of commit 02225e4, indexed Jun 4, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentsgdu.md

Repo facts: type, license, health, rank, contributors
gdu facts
TypeApp
LicenseMIT
Code health6.8 / 10 (Fair)
Health rank#155 of 4,000+ indexed repos
Last commitJun 2, 2026
Bus factor1
Size158 files, 18,841 lines

Explore gdu

Ask about this code in your agent

This connects Repowise to gdu's code. It does not install gdu.

Useful if you want to change or fork gdu: your agent can ask how it is put together and get answers that cite its files.

Ask about gdu

Answers come from gdu's README and source, with the files they cite. Two free answers a day without an account.

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of dundee/gdu from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

dundee/gdu FAQ

What is gdu?

gdu is a fast disk usage analyzer with a console interface, written in Go. It shows how much space directories and files use on a disk. It can also print statistics or export usage data as JSON.

How does gdu work?

gdu scans a directory tree and shows the results in an interactive terminal view by default. In non-interactive mode without the --top or --depth flags, it tracks only top-level directory totals, so memory use stays constant.

What language is gdu written in?

gdu is written in Go. Go files make up most of the code in the repository.

How is the gdu code organized?

The entry point is cmd/gdu/main.go, and most core code lives in the pkg directory. The tui directory holds the terminal user interface, and the internal directory holds shared helpers.

Who is gdu for?

gdu is intended primarily for SSD disks, where it can fully utilize parallel processing. HDDs work as well, but the performance gain is smaller.

What license does gdu use?

gdu is licensed under MIT, as given by its license identifier MIT.

Code health

6.7out of 10Fair

Hotspots average 5.6, the place fixes pay off most.

On the leaderboards:#17 of 28 Go repos

Key features of gdu

  • Analyzes disk usage and is aimed mainly at SSD disks, where it can use parallel processing, although HDDs also work.
  • Offers interactive, non-interactive and export modes, with interactive mode as the default.
  • Reads an optional YAML configuration file that sets options such as colors, sorting and styling.
  • Saves analysis results to SQLite or BadgerDB storage so they can be reloaded without running the analysis again.
  • Marks entries with one-character flags for read errors, symlinks and sockets, hard links, and empty directories.
  • Can delete items in the background or in parallel, as an experimental option.

How dundee/gdu works

The program starts from cmd/gdu/main.go, which hands control to the app code in cmd/gdu/app/app.go. The pkg directory holds most of the core code, and pkg/analyze/sqlite.go and pkg/analyze/stored.go deal with saving analysis data to a database so it can be reloaded later. The tui directory contains the terminal user interface used in interactive mode. Non-interactive mode is chosen automatically when no TTY is detected, and export mode with -o writes all usage data as JSON, which the -f flag can read back. The internal directory holds shared helpers such as internal/common/app.go.

The codebase has 158 files and 1,371 symbols in 7 modules, led by Go, Dockerfile and Makefile. Code health is 6.7 out of 10, rated fair.