JointFPM
Recurrent-event modelling settles, with mean_no() promoted to stable.
Comparison · Infra & APIs
statsExpressions vs surveytidy
A side-by-side editorial comparison of statsExpressions and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
statsExpressions vs surveytidy: at a glance
What is statsExpressions?
A statistics backend whose release history is mostly other people's weather
statsExpressions produces the tidy dataframes and plotmath expressions that ggstatsplot prints onto plots, and that position defines its changelog. Six of its ten most recent versions exist to absorb API changes in easystats, dplyr or purrr. Version 2.0.0 is the exception, cut to accompany ggstatsplot's own 1.0.0 and carrying pairwise Fisher's exact post hocs for contingency tables.
What is surveytidy?
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
statsExpressions vs surveytidy: editorial side-by-side
statsExpressions
0.0INFRA · APIS
A statistics backend whose release history is mostly other people's weather
◆ Current state
statsExpressions produces the tidy dataframes and plotmath expressions that ggstatsplot prints onto plots, and that position defines its changelog. Six of its ten most recent versions exist to absorb API changes in easystats, dplyr or purrr. Version 2.0.0 is the exception, cut to accompany ggstatsplot's own 1.0.0 and carrying pairwise Fisher's exact post hocs for contingency tables.
◆ Where it's heading
This is a component settling into place beneath a larger package rather than a product with its own roadmap. New statistical content arrives rarely and narrowly — an exact-p toggle, one post-hoc function — while the recurring work is keeping expressions correct as the easystats stack shifts underneath. The one bug class it keeps returning to is rendering: p-values of exactly zero, decimal commas that plotmath parses as list separators.
◆ Prediction
Coupled this tightly, the next release is most likely another compatibility pass timed to an easystats or ggstatsplot version rather than new tests. Nothing in these entries signals an independent feature direction.
surveytidy
0.0INFRA · APIS
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
◆ Current state
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
◆ Where it's heading
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
◆ Prediction
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
Alternatives to statsExpressions and surveytidy
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 statsExpressions or surveytidy.
CptNonPar
Nonparametric change point detection swaps p-values for importance scores.
ggprism
A Prism-styled ggplot2 theme in maintenance, now surviving ggplot2 4.0.
TrendLSW
Wavelet trend estimation tightens the defaults it shipped with.
mmpca
Back from CRAN removal under a new maintainer, with the compiled layer rebuilt.
mice
mice can finally predict, not just estimate, from multiply imputed data.
See all statsExpressions alternatives → · See all surveytidy alternatives →
Recent activity from statsExpressions and surveytidy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveytidymutate() syncs metadata for across() recodes
- 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
- 3mo agostatsExpressionsPairwise Fisher's post hocs for contingency tables
- 4mo agostatsExpressionsInternal maintenance only, no user-facing changes
- 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
- 6mo agostatsExpressionsAdapts to dplyr 1.2.0 and purrr 1.2.1
- 6mo agostatsExpressionsAdapts to changes in the easystats packages
- 1y agostatsExpressionsFixes p-value rendering when p is exactly zero
- 1y agostatsExpressionscentrality_description() follows the new easystats API
Frequently asked questions
What is the difference between statsExpressions and surveytidy?
They serve adjacent needs but don't currently overlap on shipped themes. statsExpressions and surveytidy 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.
Is statsExpressions better than surveytidy?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. statsExpressions and surveytidy 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.
What are the best alternatives to statsExpressions?
Top statsExpressions alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "statsExpressions alternatives" section above for the current picks, or visit /alternatives/statsexpressions for the full list with editorial commentary on each.
What are the best alternatives to surveytidy?
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.