Retool
Retool is retiring standalone Assist while folding the same capability into the app builder.
A side-by-side editorial comparison of forestploter and L1centrality — release velocity, themes, recent moves, and the top alternatives to consider.
A forest plot package that keeps handing users control of one more graphical detail.
forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.
The direction has been consistent for four years: whatever a user might want to restyle eventually becomes an argument. Point size stopped being transformed, cell height adjustment was removed as unwanted, legends gained size, column, and fill-order control, and vertical lines learned to extend the full plot height and to draw beneath the whiskers. The one structural move was 1.1.0, which let callers supply their own confidence-interval and summary drawing functions — turning a fixed renderer into an extensible one. Everything since has been the arguments that extensibility did not cover.
The latest release deprecates theme parameters rather than adding them, which suggests the next one consolidates the theme surface that has grown for four years rather than extending it further.
L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.
The package has moved from defining measures to operationalizing them. 0.5.0 was the inflection: parallel local computation and list-valued group input both target users running these measures over many vertex sets or large graphs rather than illustrating them on one. The same release renamed weight_transform and eta to edge_weight_transform and vertex_weight, and added an explicit message when a distance matrix is received — the signature of a maintainer fielding the same misuse repeatedly.
The last two releases carry no functional change, so the near-term path is maintenance rather than new measures; a 0.6.0 would most likely extend parallelism beyond L1centLOC to the other computationally heavy variants.
Other Infra & APIs 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 forestploter or L1centrality.
Retool is retiring standalone Assist while folding the same capability into the app builder.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all forestploter alternatives → · See all L1centrality alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. forestploter and L1centrality 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. forestploter and L1centrality 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 Infra & APIs products to evaluate alongside.
Top forestploter alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "forestploter alternatives" section above for the current picks, or visit /alternatives/forestploter for the full list with editorial commentary on each.
Top L1centrality alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "L1centrality alternatives" section above for the current picks, or visit /alternatives/l1centrality for the full list with editorial commentary on each.