Code quality
The module catalog divides both repositories into modules, each with one responsibility. The map shows how their code depends on each other and what there is to clean up; the tables show what CI measured on the commit running here. How this is measured
CI results
This comes from quality/evidence.json, written by a run of the checks on this computer. It is not the CI result of a commit.
Code map
Cleanup candidates
What the map points at: code that looks unused, code that exists twice and files that grew long. These are places to look, not failures. Each row opens its place on the map.
Module boundaries
What the map cannot see
The map links code by reading it, without running it. These are the places where reading is not enough, so a missing line there does not prove that two modules are independent.
CI results by module
Criticality is declared in the catalog from the impact of a failure, not measured. Duplicated blocks are code clones of at least 10 lines; the status says whether any is new since the reviewed baseline. There is no combined quality score. For the coverage of each file, colour the map by branch coverage on Files.