Show HN: Visualize the Entropy of a Codebase with a 3D Force-Directed Graph

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • dep-tree

    tool for helping developers keep their code bases clean and decoupled. It allows visualising a "code base entropy" using a 3d force-directed graph of files and the dependencies between.

  • The portion of the code in charge of rendering lives inside the `internal/entropy` (

    Force-directed is an algorithm for displaying graphs in a 2d or 3d space, which simulates attraction/repulsion based on the dependencies between the nodes, the wikipedia page explains it really well

    > Love it, I think dependency trees are super underused data for static analysis.

    Definitely, specially for evaluating "the big picture" of a codebase

  • git-of-theseus

    Analyze how a Git repo grows over time

  • A tangentially related tool you can use to look at a repo over time is Git of Theseus[1]. It shows things like "what percentage of the code in this repo survives 6 months.


  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • Gource

    software version control visualization

  • This is really cool. And as OP pointed out, I really like the pipeline integration. Like when linting catches function-level complexity, but in a cross functional way. I prefer to think of programs in layers where the top layers can import lower layers, but never the other way (and also very cautious on horizontal imports). Something like this would help track that.

    From the visualization perspective, it reminds me a lot of Gource. Gource is a cool visualization showing contributions to a repo. You see individual contributors buzzing around updating files on per-commit and per-merge.

  • black

    The uncompromising Python code formatter

  • Perfect, that worked, thank you!

    I thought this could be solved by changing the directory to src/ and then executing that command, but this didn't work.

    This also seems to be an issue with the web app, e.g. the repository for the formatter black is only one white dot

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts