Skip to content

Wingbox 0.2.0

Choose a tag to compare

@it-baron it-baron released this 15 Nov 23:05
· 13 commits to main since this release
4e6865f

wingbox build now gives people something to read and to look at, not only a graph for the agent.

New

  • Report: wingbox-out/REPORT.md with the key findings, the most depended-on files, the layers, the boundary violations and where to start reading.
  • Map: wingbox-out/map.html, one file that works offline. Click a file to see its blast radius on rings, switch to the 3D view of the layers, link to a file with map.html#select=<file>.
  • Docker: docker run --rm --network none -v "$PWD":/repo wingbox builds the graph, the report and the map with nothing installed on the machine and no network access (build the image from the Dockerfile).
  • JavaScript files (.js, .jsx, .mjs, .cjs) are modules.
  • TypeScript: inherited tsconfig paths, packages of the same repository imported by name, imports through a build output folder.
  • boundaries separates violations that rest on folders from candidates that rest on a guessed layer.

Checked against the source

The import edges were compared with independent import resolvers on open-source repositories. File-to-file precision / recall of this version:

Code Precision Recall
Rust compiler, 1,462 dependencies 1.000 1.000
Rust command-line tool 0.995 1.000
TypeScript server, 919 dependencies 1.000 0.999
TypeScript and JavaScript tool, 361 dependencies 1.000 0.997

Fixed on the way: a hang of the graph reader on a quoted bracket, module ID collisions between files that differ only by extension, Rust paths without use and inside macros, generic arguments read as the implemented trait, classes linked to a file that only defines a class of the same name, and the relation label printed by impact. The full list is in CHANGELOG.md.

Install

pipx install wingbox      # or: uvx wingbox --help
wingbox build .
wingbox impact path/to/file.py