Where this repository actually uses vfairness
A live map of every public library symbol — that is, every function or class the
vfairness package exports (such as CorrelationReducer or
demographic_parity_difference) — against the surfaces that consume it. Use it
to audit coverage, find unused capabilities, and trace which library function powers each step.
Navigator step → Library module → SVG template
Predictive AI and Generative AI audits run different canonical pipelines. Toggle between them to see which library modules each step invokes and which SVG templates those modules render. Empty steps are kept visible — they mark gaps where the library could grow.
Edge thickness = number of symbols flowing on that link. Hover any line for the exact count.
Every library symbol, every call site
Each row is a symbol — a public function or class exported by the
vfairness package. Filter by track, SVG template or status; sort any column.
| Symbol | Library module | Navigator step(s) | Tracks | SVG templates | Uses | Status |
|---|
All Navigator entry points
Every file or notebook that imports vfairness. Click any row to focus the matrix.
Templates produced by tracks
Of every Jinja SVG template the library ships, how many are produced by at least one Navigator track. Orphans are listed for review. One caveat: _shared_defs is an internal defs partial the chart templates include, not a chart, so no track can ever produce it; if it appears below it is a counting artifact, not a real orphan.
How this map stays honest
scripts/build_usage_map.py. It walks every Navigator-class
entry point in this repository, joins every imported symbol against
vfairness-manifest.json (which carries the canonical capability → SVG template mapping),
and emits docs/site/data/usage_map.json.
notebooks/. A
symbol marked unused is one that no entry point in this repository reaches. It is not a
claim that nothing anywhere calls it, and this page does not make that claim. Entry points outside
this repository are not scanned and are not counted either way: they are not part of what you are
holding, so a number derived from them would not be one you could check.
The map is rebuilt by CI, not by hand. The
Library Usage Map workflow runs on every push to main that touches the
library source, the manifest or the builder, on a nightly schedule, and on demand. It regenerates
the JSON, commits it only if it changed, and then deploys the site, so the numbers you are reading
were produced by the same run that shipped this page. A rebuild that finds nothing new is discarded
rather than committed, so the Generated date above is when this data last
changed, not when it was last checked: an older date means checked and unchanged.
The upstream input, vfairness-manifest.json, is separately gated by
test_manifest_is_fresh in the test suite, so it cannot drift underneath the map.
Maintainer How each view gets refreshed, and which one needs a human
Library Usage Map workflow rebuilds it
on every push to main that touches the library source, the manifest or a
builder, and again on a nightly schedule. It commits only when the content actually
changed, then deploys the site from the same run. Nothing to do by hand.
This box is a label, not a lock. These pages are served as static files with no authentication, so everything above is readable by anyone; credentials and the internal wiring they configure are deliberately not described here.