The scan takes seconds. Convincing everyone else takes longer.
So the output is a document, not a dashboard you have to demo. One score for the repository, every dimension scored underneath it, and each finding priced by what clearing it costs. Read the real one below, in print form and on a phone, before you send anyone a link.
Explore the real sample · Acme Checkout, health 72
Page one is a bug in your code, already corrected.
The cover is not a stock illustration. It is your highest-severity mechanical finding shown before and after, so the first thing anyone reads is evidence rather than a claim. The seven pages after it narrow from one number to a named line.
print, web and phone are three renderers over one payload · nothing is written for the document that the scan did not produce
Whoever pushes back will go straight to the numbers.
Three things about the document that hold up when they do.
Every number came from a field, not a narrative.
Each score, count and citation maps to something the scan emitted. Findings carry the file and line, so an engineer can open the file and disagree with a specific claim rather than the report as a whole.
The backlog arrives with hours next to it.
Findings are sorted by what clearing them costs, and the ones that correct themselves lead. That turns "we should clean this up" into a line you can schedule against a sprint, and the part that is free is visible as free.
Where it is capped, it says so on the page.
Long lists are truncated with the cap printed next to them, clean compliance frameworks are marked checked and passed rather than dropped, and the methodology page states how the score is built.
validated by re-parse and lint before it prints · how the scan works · measured against other scanners