easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of tune and yardstick — release velocity, themes, recent moves, and the top alternatives to consider.
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
yardstick made fairness metrics a first-class part of tidymodels evaluation
yardstick supplies the metrics tidymodels evaluates models with. Its recent history is metric expansion into areas the package did not originally cover - survival analysis, model fairness, and in 1.4.0 a batch of regression and classification metrics filling remaining gaps - alongside a long deprecation cycle that finally turned errors on in 1.4.0.
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
yardstick supplies the metrics tidymodels evaluates models with. Its recent history is metric expansion into areas the package did not originally cover - survival analysis, model fairness, and in 1.4.0 a batch of regression and classification metrics filling remaining gaps - alongside a long deprecation cycle that finally turned errors on in 1.4.0.
The direction is coverage plus extensibility. Rather than adding fairness metrics one at a time, 1.3.0 shipped new_groupwise_metric() so group-aware metrics can be defined for the problem at hand, which is the more durable contribution. The parallel thread is removing hidden state: the event_first global option, deprecated in 0.0.7, took until 1.4.0 to become an error.
Expect the groupwise constructor to attract more fairness definitions than the three shipped, and the developer-facing metric creation helpers deprecated in 1.2.0 to be removed next; core metric coverage now looks close to complete.
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 tune or yardstick.
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
discrim settled into a thin engine shim after handing its model definitions to parsnip.
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
See all tune alternatives → · See all yardstick alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. tune and yardstick are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. tune and yardstick are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.
Top yardstick alternatives in Analytics are ranked by recent ship velocity. Browse the "yardstick alternatives" section above for the current picks, or visit /alternatives/yardstick for the full list with editorial commentary on each.