TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of fracture and gdverse — release velocity, themes, recent moves, and the top alternatives to consider.
fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.
A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.
gdverse is turning geographical detector methods into inference, not just point estimates.
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.
This is a completed utility. Its arc ran from correctness — floating-point rounding, exhaustive tests across millions of fractions — through API tightening, to edge-case tolerance, and then stopped. The 2026 release contains no user-visible change at all; it exists because CRAN's toolchain moved, which is the characteristic maintenance mode of a small package that does one thing correctly.
Nothing in these entries suggests new functionality; expect further releases only when R or CRAN policy forces one, as this one did.
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
The arc is from computing detector statistics to qualifying them. Confidence intervals, significance reporting and non-centrality parameter estimation are all about telling users how much to trust a q-value, which is the gap between a research script and a package other people cite. The Python-dependency work is the recurring tax on that: several releases exist mainly to keep reticulate-backed models passing checks.
Expect the experimental q-statistic confidence intervals to be promoted to a stable, documented interface across the detector family, since the last two releases have both worked on their robustness and reporting.
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 fracture or gdverse.
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 fracture alternatives → · See all gdverse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fracture and gdverse 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. fracture and gdverse 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 fracture alternatives in Analytics are ranked by recent ship velocity. Browse the "fracture alternatives" section above for the current picks, or visit /alternatives/fracture for the full list with editorial commentary on each.
Top gdverse alternatives in Analytics are ranked by recent ship velocity. Browse the "gdverse alternatives" section above for the current picks, or visit /alternatives/gdverse for the full list with editorial commentary on each.