TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of churon and reliagrowr — release velocity, themes, recent moves, and the top alternatives to consider.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
A reliability growth package put its models behind an MCP server for AI assistants to call.
ReliaGrowR fits reliability growth models to failure data — Crow-AMSAA and Duane, with maximum likelihood estimation, confidence bounds, prediction, and reliability demonstration test planning. The last year widened it well past growth curves into repairable systems: parametric non-homogeneous Poisson process fitting with automatic change point detection, non-parametric mean cumulative function estimation, and system exposure calculation. The most recent release adds goodness-of-fit statistics and exposes the package's functions as Model Context Protocol tools.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.
Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.
ReliaGrowR fits reliability growth models to failure data — Crow-AMSAA and Duane, with maximum likelihood estimation, confidence bounds, prediction, and reliability demonstration test planning. The last year widened it well past growth curves into repairable systems: parametric non-homogeneous Poisson process fitting with automatic change point detection, non-parametric mean cumulative function estimation, and system exposure calculation. The most recent release adds goodness-of-fit statistics and exposes the package's functions as Model Context Protocol tools.
Two arcs run in parallel. The statistical one is a steady march from plotting a growth curve to modelling recurrent failures properly — segmented NHPP models that detect their own change points, Nelson-Aalen estimation, Cramér-von Mises and Kolmogorov-Smirnov statistics for judging the fits. The interface one is newer and more unusual: the package now ships an MCP server, and its sibling plotting package followed with one two weeks later, so this is a deliberate direction across the maintainer's reliability suite rather than a single experiment. Naming and S3 conventions were cleaned up early, which is what made a uniform tool surface plausible later.
Given the sibling packages moved to MCP within weeks of each other, the remaining tools in the suite are the obvious next candidates; on the statistical side, goodness-of-fit having just arrived suggests model comparison and selection helpers are the natural follow-on.
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 churon or reliagrowr.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all churon alternatives → · See all reliagrowr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. churon and reliagrowr 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. churon and reliagrowr 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 churon alternatives in Analytics are ranked by recent ship velocity. Browse the "churon alternatives" section above for the current picks, or visit /alternatives/churon for the full list with editorial commentary on each.
Top reliagrowr alternatives in Analytics are ranked by recent ship velocity. Browse the "reliagrowr alternatives" section above for the current picks, or visit /alternatives/reliagrowr for the full list with editorial commentary on each.