Knowing the shape of a whole repository, not only its changes

The problem

Pull request reviews see a change at a time. Nobody sees the building: the import that runs the wrong way three layers down, the service the code calls that nothing documents, the runtime that went out of support last year.

What visualdiff does

• Pick a repository from a connected host, or paste any public repository link; the default branch is read unless you name another. The branch is downloaded as one archive, read in memory and never kept.
• The blueprint draws its layers, packages and imports, follows one request through, and grades the design in nine areas, every check listed with where it failed and the practice it comes from.
• The rules a pull request meets run over every line; the map shows how far each module sits from the internet and what depends on it, and the matrix shows the imports that run the wrong way.
• Each review of a branch is kept: compare any two with the changes painted on the blueprint, or draw several repositories together to see which call which and what they share.