RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of factoextra and posteriordb-r — release velocity, themes, recent moves, and the top alternatives to consider.
factoextra woke from six years of silence and stopped being a FactoMineR front-end
factoextra supplies the fviz_* grammar most R users reach for when plotting PCA, correspondence analysis and clustering results. It sat effectively dormant from 2020 to early 2026, then shipped three releases in five months that resolved a six-year issue backlog, decoupled it from its original backends, and taught it to plot UMAP and t-SNE embeddings. The current version also reaches into tidymodels, plotting a PCA fitted inside a recipe or workflow directly.
posteriordb's R client ships a test-file fix and nothing else.
posteriordb-r is the R interface to the posteriordb collection of reference Bayesian posteriors, used for benchmarking inference algorithms. The single release in view fixes Stan syntax in test files. Neither the posterior collection nor the client API changes.
factoextra supplies the fviz_* grammar most R users reach for when plotting PCA, correspondence analysis and clustering results. It sat effectively dormant from 2020 to early 2026, then shipped three releases in five months that resolved a six-year issue backlog, decoupled it from its original backends, and taught it to plot UMAP and t-SNE embeddings. The current version also reaches into tidymodels, plotting a PCA fitted inside a recipe or workflow directly.
The direction is from wrapper to visualization layer. as_factoextra_pca() turned the fviz_pca_* family into something that consumes coordinates from anywhere — cmdscale, vegan, a custom decomposition, a recipes step — rather than only FactoMineR objects, and the vignette on extending factoextra to new backends says the maintainer intends others to plug in. The embedding support shows the same care: no scree plot, no correlation circle, and a convex hull instead of a confidence ellipse, because an embedding does not preserve the metric an ellipse would assume.
With recipes and workflows already wired in, the next likely step is covering more tidymodels dimension-reduction steps (step_umap, step_ica, step_pls) through the same as_factoextra_pca() entry point rather than adding new fviz_* functions per method.
posteriordb-r is the R interface to the posteriordb collection of reference Bayesian posteriors, used for benchmarking inference algorithms. The single release in view fixes Stan syntax in test files. Neither the posterior collection nor the client API changes.
One patch-level entry gives little to read. What it does say is that upkeep here tracks Stan's evolving syntax rather than the database's contents — the client's job is to stay compatible with the language the reference models are written in. Whether the collection itself is growing is not visible from this feed.
Expect further compatibility patches as Stan syntax deprecations land; the entries give no signal on new posteriors or API changes.
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 factoextra or posteriordb-r.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all factoextra alternatives → · See all posteriordb-r alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. factoextra is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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. factoextra is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 factoextra alternatives in Analytics are ranked by recent ship velocity. Browse the "factoextra alternatives" section above for the current picks, or visit /alternatives/factoextra for the full list with editorial commentary on each.
Top posteriordb-r alternatives in Analytics are ranked by recent ship velocity. Browse the "posteriordb-r alternatives" section above for the current picks, or visit /alternatives/posteriordb-r-r for the full list with editorial commentary on each.