rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of statpsych and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
A statistics catalogue for psychology that grows by the release and rarely changes shape.
statpsych supplies confidence intervals, hypothesis tests, power calculations and sample-size planning for the designs psychology researchers actually run, exposed as several hundred small named functions rather than a modelling framework. Version 2.0.0 adds eight functions across logistic model performance, Kendall tau-a intervals and sample sizes, intraclass correlation testing, Geary kurtosis and Mann-Whitney power, and retires three names in favour of generalised replacements. The major version number reflects those removals rather than a change in how the package is used.
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
statpsych supplies confidence intervals, hypothesis tests, power calculations and sample-size planning for the designs psychology researchers actually run, exposed as several hundred small named functions rather than a modelling framework. Version 2.0.0 adds eight functions across logistic model performance, Kendall tau-a intervals and sample sizes, intraclass correlation testing, Geary kurtosis and Mann-Whitney power, and retires three names in favour of generalised replacements. The major version number reflects those removals rather than a change in how the package is used.
Every release in this window is the same shape: a list of new functions, occasionally a rename. The package grows by filling cells in a grid of estimand, design and inferential goal, and 2.0.0 is notable only for finally deleting the three names its generalised replacements had superseded. That makes it a reference library whose value is coverage and stability, not direction, and the entries give no sign of that changing.
Expect the accretion to continue along the same axes, with sample-size and power counterparts filled in for estimands that currently have interval functions but no planning ones. The 2.0.0 deletions suggest occasional consolidation passes when a generalised function makes older specific ones redundant.
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
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 statpsych or writeAlizer.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
Spatial thinning grows a result object, and the API breaks to make room for it
See all statpsych alternatives → · See all writeAlizer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. statpsych and writeAlizer 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. statpsych and writeAlizer 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 statpsych alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "statpsych alternatives" section above for the current picks, or visit /alternatives/statpsych for the full list with editorial commentary on each.
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.