metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of cfr and CRediTas — 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.
A CRediT author-statement generator that renamed itself, then went quiet for two years.
CRediTas turns a contributor-roles table into a CRediT Author Statement for a paper. The 0.2.0 release in April 2023 did the heavy lifting — package rename, a full object_verb() API rename, and output that drops straight into R Markdown or Quarto. The 0.3.0 release in August 2025 is the only activity since and carries no changelog text beyond a pointer to NEWS.md.
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.
CRediTas turns a contributor-roles table into a CRediT Author Statement for a paper. The 0.2.0 release in April 2023 did the heavy lifting — package rename, a full object_verb() API rename, and output that drops straight into R Markdown or Quarto. The 0.3.0 release in August 2025 is the only activity since and carries no changelog text beyond a pointer to NEWS.md.
Development front-loaded a breaking cleanup during rOpenSci review and has coasted since. The design bet made in 0.2.0 — return a string for inline use rather than write a file — pointed the package at literate authoring workflows rather than at standalone scripts, and nothing since has moved away from it. The empty 0.3.0 note makes the current direction impossible to read from the feed.
Too little is published to call the next move; the 0.3.0 entry would need to carry its actual changes for the trajectory to be readable from the changelog at all.
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 CRediTas.
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 CRediTas 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 CRediTas 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 CRediTas 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 CRediTas alternatives in Analytics are ranked by recent ship velocity. Browse the "CRediTas alternatives" section above for the current picks, or visit /alternatives/creditas for the full list with editorial commentary on each.