humind
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
A side-by-side editorial comparison of baseq and coga — release velocity, themes, recent moves, and the top alternatives to consider.
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
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.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
The visible history is a package assembled quickly and then left alone. Across the 0.1.x tags the notes are a printed inventory of exported functions rather than a changelog, with consecutive versions restating the same list unchanged, so the actual increments have to be inferred by diffing those inventories: file-level cleaning and GC content arrived at 0.1.3, and the FASTA and FASTQ readers, writers and converters at 0.1.1. What the 2.0 release contains is not stated anywhere in the feed, which makes the most significant-looking tag here also the least legible.
Nothing in these entries supports a confident prediction. The reappearance of activity after three years and the addition of a CI workflow suggest maintenance has resumed, but until a release describes its own contents there is no basis for saying in what direction.
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.
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 baseq or coga.
The MSNI humanitarian needs framework as code, rewritten and re-broken every year
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.
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. baseq and coga 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. baseq and coga 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 Infra & APIs products to evaluate alongside.
Top baseq alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "baseq alternatives" section above for the current picks, or visit /alternatives/baseq for the full list with editorial commentary on each.
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.