inlabru
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
A side-by-side editorial comparison of coga and humind — release velocity, themes, recent moves, and the top alternatives to consider.
A gamma-convolution density package that reached completion in 2018 and has coasted since.
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
humind turns household survey data into Multi-Sector Needs Index severity scores across WASH, Protection, SNFI, Food Security, Education and Health. Its version line tracks the annual MSNI framework revision — 2024.x, 2025.x, 2026.x — with narrow correctness patches between rollouts. v2026.2.0 is the current rollout and the most structural one in the visible history: water-quantity scoring moved out into a new mandatory prerequisite, food-security severity now comes from a different matrix, and the impactR4PHU runtime dependency is gone.
coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.
This is a finished package being kept alive rather than developed. The releases track external pressure exactly: CRAN documentation requirements, compiler warnings, Rcpp API changes. Its maintenance is visibly shared with smam, the same maintainer's animal-movement package, which received the same email update, the same format-security fix and the same Rcpp guard within a minute or twenty of coga each time. Neither package is being extended; both are being kept installable.
Expect nothing but CRAN and toolchain maintenance, arriving whenever Rcpp or R's check requirements change, and arriving alongside smam. There is no signal in these entries of planned functional work.
humind turns household survey data into Multi-Sector Needs Index severity scores across WASH, Protection, SNFI, Food Security, Education and Health. Its version line tracks the annual MSNI framework revision — 2024.x, 2025.x, 2026.x — with narrow correctness patches between rollouts. v2026.2.0 is the current rollout and the most structural one in the visible history: water-quantity scoring moved out into a new mandatory prerequisite, food-security severity now comes from a different matrix, and the impactR4PHU runtime dependency is gone.
Two things move together. The framework content is revised yearly — indicators added, weights corrected, instruments swapped — and the package keeps absorbing pipeline it used to delegate, most visibly by vendoring add_fcs(), add_hhs(), add_rcsi(), add_lcsi() and add_fcm_phase() locally rather than importing them. Each rollout is explicitly breaking and the release notes have grown per-function 'Action:' instructions, which reads as maintainers who expect every downstream dashboard to need rewiring on the same annual clock.
The 2025 line settled into narrow patches immediately after its rollout — 1.2, 1.3 and 1.4 fixed a separator argument, a schema rename and a shelter misclassification rather than adding indicators. Expect the 2026 line to do the same: correctness fixes against the new WASH, FCLCM and shelter-damage logic before any further framework change.
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 coga or humind.
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.
Animal-movement models in R, where new stochastic processes arrive years apart.
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
Package citation for R documents, quietly growing to meet Quarto.
Accessible government spreadsheets in R, rebuilt on openxlsx2 and renamed along the way.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. humind is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. humind is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top coga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "coga alternatives" section above for the current picks, or visit /alternatives/coga for the full list with editorial commentary on each.
Top humind alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "humind alternatives" section above for the current picks, or visit /alternatives/humind for the full list with editorial commentary on each.