← Back to home
Comparison · Analytics

factoextra vs hdnom

A side-by-side editorial comparison of factoextra and hdnom — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r

factoextra vs hdnom: at a glance

Featurefactoextrahdnom
SectorAnalyticsAnalytics
Velocity score3.85.0
Sparks · 30d10
Top themesdimension reduction, r, ggplot2, clusteringsurvival analysis, r, regularization, nomograms
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is factoextra?

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.

Read the full factoextra trajectory →

What is hdnom?

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.

Read the full hdnom trajectory →

factoextra vs hdnom: editorial side-by-side

F
factoextra
ANALYTICS
3.8

factoextra woke from six years of silence and stopped being a FactoMineR front-end

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

H
hdnom
ANALYTICS
5.0

hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to factoextra and hdnom

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.

See all factoextra alternatives → · See all hdnom alternatives →

Recent activity from factoextra and hdnom

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 18d agohdnomhdnom 6.2.1
  2. 18d agohdnomhdnom 6.2.0 pins Cox tie handling ahead of glmnet's migration
  3. 22d agofactoextrafactoextra 2.2.0 adds UMAP and t-SNE plotting, plus tidymodels recipes
  4. 1mo agofactoextrafactoextra 2.1.0 decouples its plots from any specific backend
  5. 5mo agofactoextrafactoextra 2.0.0 ends a six-year dormancy with breaking modernization
  6. 1y agohdnomhdnom 6.1.0 exposes lambda selection after a glmnet normalization change
  7. 1y agohdnomhdnom 6.0.4
  8. 2y agohdnomhdnom 6.0.3
  9. 3y agohdnomhdnom 6.0.2
  10. 6y agofactoextrafactoextra 1.0.7
  11. 6y agofactoextrafactoextra 1.0.6
  12. 8y agofactoextrafactoextra 1.0.5

Frequently asked questions

What is the difference between factoextra and hdnom?

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.

Is factoextra better than hdnom?

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.

What are the best alternatives to factoextra?

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.

What are the best alternatives to hdnom?

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.