WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of jstable and L1centrality — release velocity, themes, recent moves, and the top alternatives to consider.
A clinical table generator paying down years of edge cases in survey-weighted models
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
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.
jstable turns regression and survival models into the formatted tables medical papers publish, wrapping coxph, glm, geeglm, lmer and their survey-weighted counterparts. The recent line is almost entirely correction work, concentrated in two places: the .display family and the TableSubgroup family. Version 1.3.25 alone fixed quasibinomial support for survey-weighted logistic regression, automatic factor-to-numeric outcome conversion for svyglm, weighted-versus-original sample counts in the n row, data.table input handling, and Overall column labelling.
Each CRAN release bundles several GitHub patch versions, so the notes read as rolled-up fix lists rather than feature announcements. The substantive thread is pcut.univariate, introduced across seven display functions in 1.3.11 to allow multivariable analysis restricted to significant variables, and repaired repeatedly since as it collided with interaction terms, single-variable selections, clustered models and data.table inputs. The survey-weighted path is the other recurring source: counts, labels and family handling that worked for unweighted data kept failing once weights were involved.
Expect further patches in the survey-weighted subgroup functions, since 1.3.25 fixed four separate issues there and each recent release has surfaced more in the same area.
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 jstable or L1centrality.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
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 jstable 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. jstable 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. jstable 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 jstable alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "jstable alternatives" section above for the current picks, or visit /alternatives/jstable 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.