cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of common and epidict — release velocity, themes, recent moves, and the top alternatives to consider.
A base-R utility belt that grows one small function at a time, on no particular schedule
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
A spin-out dictionary reader for MSF epidemiological data, finding its shape on CRAN
epidict reads and applies the data dictionaries MSF field epidemiologists use to standardise outbreak and survey datasets. It was split out of the larger sitrep toolchain so the dictionary-reading and variable-renaming functions could ship on CRAN independently. Three releases in roughly two months have taken it from that initial separation to handling intersectional dictionaries.
common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.
The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.
Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.
epidict reads and applies the data dictionaries MSF field epidemiologists use to standardise outbreak and survey datasets. It was split out of the larger sitrep toolchain so the dictionary-reading and variable-renaming functions could ship on CRAN independently. Three releases in roughly two months have taken it from that initial separation to handling intersectional dictionaries.
The arc is a package being unbundled and then reassembled as its dependencies land on CRAN. The 0.1.0 release deliberately dropped msf_dict_rename_helper() because its dependencies weren't available; 0.2.0 put it back. 0.3.0 is the first release that adds rather than restores, extending intersectional dictionary support and giving callers control over name cleaning.
Expect the next releases to keep widening dictionary coverage rather than changing the API, since the reinstatement work that dominated 0.1.0 to 0.2.0 is now finished.
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 common or epidict.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Rebuilding SAS's formatting layer in R, one format specification at a time
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all common alternatives → · See all epidict alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. common and epidict 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. common and epidict 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 common alternatives in Analytics are ranked by recent ship velocity. Browse the "common alternatives" section above for the current picks, or visit /alternatives/common for the full list with editorial commentary on each.
Top epidict alternatives in Analytics are ranked by recent ship velocity. Browse the "epidict alternatives" section above for the current picks, or visit /alternatives/epidict for the full list with editorial commentary on each.