rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
A side-by-side editorial comparison of bayestestR and timetk — release velocity, themes, recent moves, and the top alternatives to consider.
Bayesian diagnostics get stricter defaults while the Stan backend list widens
bayestestR is the diagnostics and hypothesis-testing layer of the easystats stack, and its recent releases have concentrated on two things: reporting the right uncertainty numbers by default, and accepting posterior draws from more sources. The 0.18.x line added CmdStanFit support alongside the existing rstanarm/brms paths and switched effective-sample-size reporting to tail-ESS. Bug-fix releases in between are mostly CRAN-check maintenance.
timetk swallowed anomalize whole, then went quiet for two years
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
bayestestR is the diagnostics and hypothesis-testing layer of the easystats stack, and its recent releases have concentrated on two things: reporting the right uncertainty numbers by default, and accepting posterior draws from more sources. The 0.18.x line added CmdStanFit support alongside the existing rstanarm/brms paths and switched effective-sample-size reporting to tail-ESS. Bug-fix releases in between are mostly CRAN-check maintenance.
The package is converging on a single posture: work with raw MCMC draws from anywhere, and report the diagnostic that actually governs the interval being shown. Successive releases have swapped defaults rather than added surface area, and the efficiency work in 0.16.x aimed squarely at large brms and rstanarm fits. Output formatting is drifting toward the shared easystats display() and tinytable path.
Expect continued backend coverage on the Stan side and further alignment of print/display behavior with insight and the rest of easystats; the entries do not show a push into new inference methods.
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.
The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.
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 bayestestR or timetk.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.
See all bayestestR alternatives → · See all timetk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bayestestR and timetk 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. bayestestR and timetk 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 bayestestR alternatives in Analytics are ranked by recent ship velocity. Browse the "bayestestR alternatives" section above for the current picks, or visit /alternatives/bayestestr for the full list with editorial commentary on each.
Top timetk alternatives in Analytics are ranked by recent ship velocity. Browse the "timetk alternatives" section above for the current picks, or visit /alternatives/timetk for the full list with editorial commentary on each.