OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A side-by-side editorial comparison of factoextra and hdnom — 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.
hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
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.
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
The releases track two upstream pressures with no feature work of its own. glmnet is the larger one: its 4.1-9 change to how Cox cross-validation errors are normalized made lambda.1se select null models far more often, forcing hdnom to expose a rule argument and switch its examples to lambda.min. R-devel is the other, producing a steady trickle of strict-headers, deprecated-symbol and check-note fixes. The pattern is consistent — absorb the upstream change, default to whatever preserves existing behaviour, let users opt into the new one.
The cox.ties default is explicitly pinned to "breslow" to silence glmnet's migration warning, which is a deferral rather than a decision; expect a future release to flip that default to "efron" once glmnet completes the transition.
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 hdnom.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
A discrete global grid generator grew cell traversal and became a usable spatial index.
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all factoextra alternatives → · See all hdnom alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. hdnom is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. hdnom is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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 hdnom alternatives in Analytics are ranked by recent ship velocity. Browse the "hdnom alternatives" section above for the current picks, or visit /alternatives/hdnom for the full list with editorial commentary on each.