tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of StatsBase.jl and statsmodels — release velocity, themes, recent moves, and the top alternatives to consider.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
Every release in this window is a compatibility release. 0.14.2 and 0.14.3 absorbed NumPy 2, 0.14.5 fixed an import failure caused by SciPy 1.16, and 0.14.6 did the same for pandas 3.0. The only additive change across two years is Pyodide support in 0.14.4, described in its own notes as one feature and no fixes. A 0.15.0.dev0 tag exists from 2023 and has not been followed by a 0.15 release.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
This is the shape of a foundational Julia package that has reached its intended scope: the API is settled, and maintenance means keeping compat bounds current and closing long-tail correctness issues raised by users. Nothing in the feed suggests new statistical capability is being staged. The most likely reason is that new work now lands in the downstream packages that build on StatsBase rather than in StatsBase itself.
Expect more 0.34.x patches on the same rhythm — CompatHelper bumps and occasional user-reported edge-case fixes — with no signal in these entries that a 0.35 or 1.0 is being prepared.
Every release in this window is a compatibility release. 0.14.2 and 0.14.3 absorbed NumPy 2, 0.14.5 fixed an import failure caused by SciPy 1.16, and 0.14.6 did the same for pandas 3.0. The only additive change across two years is Pyodide support in 0.14.4, described in its own notes as one feature and no fixes. A 0.15.0.dev0 tag exists from 2023 and has not been followed by a 0.15 release.
The library is being kept alive rather than developed: each release answers a break introduced upstream, and the interval between them is set by the NumPy, SciPy and pandas release calendars rather than by anything statsmodels is building. Two consecutive releases whose stated purpose was restoring the ability to import the package is the sharpest available signal about maintainer bandwidth. The 0.15 line remains a dev tag with no visible progress toward a release.
The next release is most likely another compatibility patch triggered by a NumPy, SciPy or pandas major, and nothing in these entries indicates 0.15 is close.
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 StatsBase.jl or statsmodels.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
See all StatsBase.jl alternatives → · See all statsmodels alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — statistics, maintenance — within Analytics. StatsBase.jl and statsmodels 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. StatsBase.jl and statsmodels 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 Analytics products to evaluate alongside.
Top StatsBase.jl alternatives in Analytics are ranked by recent ship velocity. Browse the "StatsBase.jl alternatives" section above for the current picks, or visit /alternatives/statsbase-jl for the full list with editorial commentary on each.
Top statsmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "statsmodels alternatives" section above for the current picks, or visit /alternatives/statsmodels for the full list with editorial commentary on each.