metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of cfr and charlatan — release velocity, themes, recent moves, and the top alternatives to consider.
cfr packaged delay-corrected severity estimation, then went quiet on maintenance.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
R's fake-data generator rebuilt its provider hierarchy so contributors can add one locale without touching the rest.
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.
The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.
The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.
charlatan generates realistic fake data — names, addresses, phone numbers, jobs, internet artefacts — across many locales, following the same model as faker in Python and Perl. The 0.6.1 release reworked the provider class hierarchy so locale-specific providers inherit from a parent, and 0.6.2 since has been a documentation rebuild that happened to surface a duplicate Norwegian phone number pattern. Activity is sparse and bursty.
The package's value scales with locale coverage, and its releases track that: early versions added data-type providers, middle versions added locales one contributor at a time, and 0.6.1 attacked the bottleneck by restructuring the class hierarchy so a locale can override a single function. Development has effectively been handed to contributors, with maintainer releases reduced to docs rebuilds and CRAN compliance.
Expect the next substantive release to be an accumulation of contributed locales and providers arriving through the new parent-provider structure, rather than maintainer-driven feature work.
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 cfr or charlatan.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all cfr alternatives → · See all charlatan alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cfr and charlatan 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. cfr and charlatan 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 cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr for the full list with editorial commentary on each.
Top charlatan alternatives in Analytics are ranked by recent ship velocity. Browse the "charlatan alternatives" section above for the current picks, or visit /alternatives/charlatan for the full list with editorial commentary on each.