Would you bet the release on this repository?
Read the codebase mechanically, and the answer is a number with its factors shown rather than a Friday-afternoon opinion.
Scoring, and reading what a model wrote
Different ways to make a codebase testify, and the last one runs in your browser right now. Anything not publicly released is marked.
Scoring
A number is only useful if you can see how it was reached and disagree with a specific term of it.
Reading with a model
Code a model wrote still needs a human owner. The review sheet makes that review mechanical, down to a hostile second opinion one prompt at a time.
The papers
Every paper carries the methodology behind any number it emits, and what the tool deliberately does not do. Pick them up from the catalogue.
- Scoring a repository so the number means somethinggandalf and gradebook
- Reviewing code that no human wrote, and still owning ita review sheet that replaces reading with mechanical checks
This theme grew out of the AI one. When a model writes the first draft, reviewing becomes the scarce skill, and the review has to be mechanical enough to trust on a tired afternoon.
A question about any of this?
Ask about any tool or paper on this page in one message, and get one reply. The tools are open source and the papers are free.