easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of tsibble and tune — release velocity, themes, recent moves, and the top alternatives to consider.
tsibble shipped one release in five and a half years - the data structure is finished
tsibble defines the tidy time-series data structure that fable and feasts are built on. The design churned heavily through 2018 and 2019, settled with the 0.9.0 move onto vctrs in mid-2020, and then went quiet: the next release, 1.2.0, arrived in February 2026 with a summary() method and some tidyselect helpers.
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.
tsibble defines the tidy time-series data structure that fable and feasts are built on. The design churned heavily through 2018 and 2019, settled with the 0.9.0 move onto vctrs in mid-2020, and then went quiet: the next release, 1.2.0, arrived in February 2026 with a summary() method and some tidyselect helpers.
This is a package that reached its final shape and stopped. The early releases are a rapid sequence of breaking changes to the key and interval metadata, each one warning that previously stored objects are corrupt; once the interval became a formal vctrs record type there was nothing structural left to change. The five-year gap is the trajectory, not a lapse.
Expect further releases to be small compatibility and convenience additions at long intervals; with the type system settled and windowing delegated to slider, there is no visible pressure for another breaking change.
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.
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 tsibble or tune.
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 tsibble alternatives → · See all tune alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tsibble and tune 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. tsibble and tune 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 tsibble alternatives in Analytics are ranked by recent ship velocity. Browse the "tsibble alternatives" section above for the current picks, or visit /alternatives/tsibble for the full list with editorial commentary on each.
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.