arXiv:2611.23329v1 Announce Type: new Abstract: Context. A conformal interval at 0.90 keeps that guarantee only at the right rank: a fresh score falls at or below the rth smallest of n with probability r/(n + 1). The libraries we study instead hand a level to a quantile function, which can land elsewhere. At n = 20, the upper end of statsforecast's interval sits at position 18.05 where rank 19 is required. Objective. Where does installed code resolve the wrong rank, at what cost in coverage, and what does it return when no rank reaches the level? Method. We audit 39 sites where a level becomes an index in 10 pinned packages, a named set rather than a systematic search. 12 are classified by running them, 11 through their shared numpy method, the rest from source. Coverage is paired against the required rank on the same scores. Results. All 7 tabular implementations reach the required rank. In darts, on one code path, coverage is unchanged (0.0000) where the ranks agree and 0.0280 to 0.0560 lower where they differ; a second archive repeats that split but not its range. Below the feasibility floor, $n < 1/\alpha - 1$, of 14 public call paths 5 silently return a finite number; the rest raise or warn. Conclusions. Quantile interfaces take only a level; statsforecast's default calibrates below its floor. 6 of 19 upstream filings have merged, one fixing a coverage shortfall. A conformance suite classifies helpers by the rank they reach, and a checklist guides review.
Continue to arXiv Software Engineering →You are being forwarded in 6s — stay on this page