# KyleBanks/depth

Visualize Go Dependency Trees

Repository: https://github.com/KyleBanks/depth
Canonical: https://ross.abutalabs.com/products/depth
Homepage: https://kylewbanks.com/blog/visualize-golang-dependency-trees-with-depth
Language: Go
License: MIT
License Family: permissive
Topics: go, dependency-tree, visualizer, command-line-tool
Last push: 2022-02-08T04:10:36+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3469, "days_push": 1667, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1083, forks 69 (observed 2026-08-28T04:03:31.267563+00:00)

## What it is
depth is a command-line tool (also usable as a Go library) that retrieves and visualizes the dependency tree of Go packages. It resolves imports for your own code, third-party libraries, and the Go standard library, printing a tree with counts of internal, external, and testing dependencies.

## Use cases
- visualize the dependency tree of a go package
- see which packages my go project actually imports
- inspect dependencies of the go standard library
- find out how many external third-party packages a go library pulls in
- analyze transitive internal dependencies of a go codebase
- print a go import tree from the terminal before vendoring

## When to choose
- You want a quick terminal-based tree view of Go package imports, including standard library packages that go list omits
- You need to inspect both your own packages and third-party/standard-library dependencies in one tool
- You want to embed dependency-tree resolution into your own Go program, since depth can also be imported as a package

## When to avoid
- You need go.mod module-level graph analysis or minimal version selection details rather than package import trees
- You need dependency visualization for languages other than Go
- You need security vulnerability auditing or license scanning of dependencies rather than structural visualization

## Facets
- artifact type: cli-tool
- maturity: stable
- function: developer-tools, cli, dependency-audit
- domain: developer-tools, programming-languages
- platform: go, cli, cross-platform, windows
- tags: go-tooling, dependency-tree, dependency-visualization, static-analysis, import-graph, package-analysis, command-line, linux, macos

## Member repositories
- KyleBanks/depth (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:31.267563+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:50:20.083294+00:00, confidence not recorded.
  - readme: https://github.com/KyleBanks/depth (fetched 2026-08-28T04:03:31.267563+00:00, sha 1ab019a3dbde)
  - homepage: https://kylewbanks.com/blog/visualize-golang-dependency-trees-with-depth (fetched 2026-08-29T12:52:58.721243+00:00, sha 74a9b8a61cc6)
- Data as of 2026-08-30T08:39:29.467469+00:00.