Baseline correctness + code style
# Correct, clean, idiomatic implementation with thorough docstring, examples, and even added input validation beyond requirements.
Five tasks I actually care about, scored by an LLM judge on correctness, code quality, and documentation. A benchmark models have to earn.
| # | model | avg score | avg latency |
|---|---|---|---|
| 01 | Claude Haiku 4.5 | 7.6 | 9440ms |
more models land here as they get run — see the CLI.
Baseline correctness + code style
# Correct, clean, idiomatic implementation with thorough docstring, examples, and even added input validation beyond requirements.
Pure documentation ability — no code at all
# Comprehensive, well-organized README covering all required sections with accurate flag documentation, clear examples, and proper Markdown/code-block formatting, though it invents extra details (hashing, exit codes) not specified in the prompt.'
Code clarity + whether the model can explain its changes
# Correct and clean refactor with meaningful names and idiomatic comprehension, but keeping 'x' as a loop variable is a minor quality lapse and the explanation table, while accurate, is fairly generic/boilerplate rather than deeply specific.
Algorithm + full docstring (Args/Returns/Raises + examples)
# Correct binary search logic and good edge-case handling, but the added `sorted(arr)` validation each call turns the algorithm into O(n log n), contradicting the claimed O(log n) efficiency and undermining the point of binary search; documentation is thorough and examples are accurate.
Class design + error handling + type hints + docs
# Response is cut off mid-implementation (post method incomplete, no usage example at bottom), making the code non-functional despite good structure and docstrings up to that point.
$ curl /api/results → 200 OK
Same data behind this page, as JSON. Cached 1h at the edge.