r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of xplainfi and ymlthis — release velocity, themes, recent moves, and the top alternatives to consider.
xplainfi treats feature importance as an estimate with error bars, not a number.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.
Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.
The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.
Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either xplainfi or ymlthis.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all xplainfi alternatives → · See all ymlthis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. xplainfi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. xplainfi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top xplainfi alternatives in Analytics are ranked by recent ship velocity. Browse the "xplainfi alternatives" section above for the current picks, or visit /alternatives/xplainfi for the full list with editorial commentary on each.
Top ymlthis alternatives in Analytics are ranked by recent ship velocity. Browse the "ymlthis alternatives" section above for the current picks, or visit /alternatives/ymlthis for the full list with editorial commentary on each.