kodebeat / papers / code
Scoring a repository so the number means something
Gandalf and gradebook.
Improve code quality is a direction, not a task. gandalf orchestrates roughly sixty external scanners into a Red/Amber/Green scorecard, and its defining behaviour is a refusal: a gate whose scanner is missing is reported as not run and excluded, because we could not check this is not a quality signal. gradebook uses no external tools at all and tells you which fix buys the most points.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the Code & repo intelligence theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.