Repository navigation
Releases
Wingbox 0.2.3
Wingbox 0.2.3.
Changes
- The README states what makes Wingbox usable inside a security perimeter: no network access, no model, no telemetry, code read and never run, an offline install. Two tests keep it true.
benchmarks/graphifyis back next tobenchmarks/impact: Wingbox and Graphify measured on the same public repositories, with the scripts and the result files.
Fixes
boundaries-summarycounts pairs of files, as the report does.- The graph of a repository without TypeScript builds as fast as in 0.2.0 again (0.2.1 and 0.2.2 resolved every import twice).
Install: pipx install wingbox or uvx wingbox. Full list: CHANGELOG.md.
Wingbox 0.2.2
Wingbox 0.2.2: a Python __init__.py is treated as its package.
Fixes
- Layers: a Python
__init__.pytakes the layer of its folder or, when no folder rule applies, the layer where most modules of the package are. The names it re-exports no longer decide its layer. On a library of 1,223 files, 89 package files had been placed in the configuration layer by a guess.
Everything of 0.2.1 is included. Install: pipx install wingbox or uvx wingbox. Full list: CHANGELOG.md.
Wingbox 0.2.1
Wingbox 0.2.1 makes the answers smaller and the layer report more exact.
Changes
analyzeandimpactprint the complete counts and list at most 200 dependent files, nearest first;--alllists every file. On a file with 650 direct dependents theanalyzeanswer went from about 55,000 tokens to about 8,800.analyzenames each dependent file once and prints paths relative to the repository root.boundariesprints a TypeScript import of types only across layers as(violation-type-only ...)and counts it apart from the violations; the report lists these imports in their own table.import.meta.resolve('<literal>')is recorded as a dependency.
Fixes
- Layers: migrations and seeds are infrastructure; a name that only begins with "test" is not a test; a file named like a layer folder (
types.ts,models.py) and the index file of such a folder take that layer. - The purpose of a file no longer depends on folders above the repository root.
- The map keeps the selected file in view after a resize, the layer names no longer overlap, and the layers keep turning while a file is selected.
wingbox <command> | headends quietly.
Install: pipx install wingbox or uvx wingbox. Full list: CHANGELOG.md.
Wingbox 0.2.0
wingbox build now gives people something to read and to look at, not only a graph for the agent.
New
- Report:
wingbox-out/REPORT.mdwith 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 withmap.html#select=<file>. - Docker:
docker run --rm --network none -v "$PWD":/repo wingboxbuilds the graph, the report and the map with nothing installed on the machine and no network access (build the image from theDockerfile). - 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. boundariesseparates 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.pyWingbox 0.1.1
The wingbox command.
pipx install git+https://github.com/aileron-tech/wingbox
cd /path/to/project
wingbox build .
wingbox impact path/to/file.pywingbox build [PATH]builds the code graph (default: the current directory).- Every query command is available as
wingbox <command>:impact,quick,analyze,search,boundary,rdepsand the others. - Relative
--root,--mapand--outputvalues are resolved against the current directory. - Python 3.11 or newer, macOS or Linux. The command installs the parsers for all supported languages.
The agent skill is unchanged: npx skills add aileron-tech/wingbox.
Wingbox 0.1.0
First tagged release of Wingbox, formerly published as codespaces.
Wingbox builds a local code graph of a repository so that AI coding agents and developers can see dependencies, call flows, architecture boundaries and the blast radius of a change before editing code.
In this release
impact <file|id> [depth] [--sexp]: the modules that depend on a file, each once at its shortest distance, and the files to read first. Readable text by default, compact S-expression facts with--sexp.- The project and the skill are named
wingbox; the repository isaileron-tech/wingbox. - "Belief map" is now "code graph":
scripts/build_code_graph.py,scripts/code_graph_search.py,.code_graph.sexp,.code_graph_cache.json.
Upgrading from codespaces
Maps built under the old names are not read. Rebuild the code graph once, delete the old generated files, and update agent instructions and ignore rules that mention the old script or file names.
Install
npx skills add aileron-tech/wingboxSupported: Python, TypeScript and TSX, Rust, C#, Java, Go, Ruby and Rails, Free Pascal and Lazarus. See the README and the changelog.