tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of fairmodels and geodist — release velocity, themes, recent moves, and the top alternatives to consider.
fairmodels sits dormant for three years, resurfacing only to satisfy a CRAN check.
fairmodels audits classification models for bias, built around fairness_check() and parity-loss metrics on top of DALEX explainers. The last substantive work dates from 2021; the 2025 release is a single-line change swapping ifelse for if/else in fairness_heatmap. Version 0.2.2 set the package's core design when it superseded metric differences with ratios.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
fairmodels audits classification models for bias, built around fairness_check() and parity-loss metrics on top of DALEX explainers. The last substantive work dates from 2021; the 2025 release is a single-line change swapping ifelse for if/else in fairness_heatmap. Version 0.2.2 set the package's core design when it superseded metric differences with ratios.
The release history describes a package that reached its intended shape early and has been custodial since — the gap from August 2022 to October 2025 carries no functional change at all. What movement exists is CRAN-driven: documentation compliance, example runtimes, coding-style notes. The fairness metrics themselves have not changed since the parity_loss corrections of 2020.
On this cadence the next release is most likely another CRAN-prompted one-liner rather than new fairness metrics; nothing in these entries points to active development.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
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 fairmodels or geodist.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all fairmodels alternatives → · See all geodist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fairmodels and geodist 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. fairmodels and geodist 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 fairmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "fairmodels alternatives" section above for the current picks, or visit /alternatives/fairmodels for the full list with editorial commentary on each.
Top geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.