← Back to home
Comparison · Analytics

cleanepi vs Tplyr

A side-by-side editorial comparison of cleanepi and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.

cleanepi vs Tplyr: at a glance

FeaturecleanepiTplyr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepiverse-trace, data-cleaning, line-list, reportingclinical-trials, tables, traceability, r-package
Last editorial update7h ago1h ago
WebsiteVisit →Visit →

What is cleanepi?

cleanepi is in the long tail of bug fixes that follows a 1.0 — and changed maintainers along the way.

cleanepi cleans and standardises epidemiological line list data — dates, subject IDs, missing values, duplicates — and produces a report of what it changed. Since 1.0.0 in mid-2024 the releases have been almost entirely corrective: date-guesser fixes, report structure fixes and matching behaviour corrections. Maintainership passed to Bubacarr Bah in 1.1.2.

Read the full cleanepi trajectory →

What is Tplyr?

Tplyr made clinical summary tables explain where every number came from.

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

Read the full Tplyr trajectory →

cleanepi vs Tplyr: editorial side-by-side

C
cleanepi
ANALYTICS
0.0

cleanepi is in the long tail of bug fixes that follows a 1.0 — and changed maintainers along the way.

◆ Current state

cleanepi cleans and standardises epidemiological line list data — dates, subject IDs, missing values, duplicates — and produces a report of what it changed. Since 1.0.0 in mid-2024 the releases have been almost entirely corrective: date-guesser fixes, report structure fixes and matching behaviour corrections. Maintainership passed to Bubacarr Bah in 1.1.2.

◆ Where it's heading

Work has concentrated on the report object and on making the cleaning functions behave predictably at the edges — case- and whitespace-insensitive missing-value matching, report elements returned as vectors instead of comma-separated strings, an argument to print a single operation's report. The underlying cleaning API has barely moved since 1.0.0, which suggests it is settled.

◆ Prediction

The report interface has been reworked repeatedly across these releases and is the most likely place for further change; the cleaning functions themselves look stable.

T
Tplyr
ANALYTICS
0.0

Tplyr made clinical summary tables explain where every number came from.

◆ Current state

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

◆ Where it's heading

Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.

◆ Prediction

Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.

Alternatives to cleanepi and Tplyr

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 cleanepi or Tplyr.

See all cleanepi alternatives → · See all Tplyr alternatives →

Recent activity from cleanepi and Tplyr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 9mo agocleanepiCase-insensitive missing-value matching and report fixes
  2. 1y agocleanepiReport elements become vectors; date parsing default restored
  3. 1y agocleanepiDate guesser corrected; empty-row indices fixed
  4. 2y agocleanepiFirst major release with cleaning and reporting
  5. 2y agoTplyrMissing-subject metadata, add_anti_join(), and nested-layer fixes
  6. 3y agoTplyrMetadata vignette fix and parenthesis hugging
  7. 3y agoTplyrDenominator logic fix ahead of CRAN release
  8. 3y agoTplyrReverse-dependency fix
  9. 3y agoTplyr1.0.0 introduces the traceability metadata framework

Frequently asked questions

What is the difference between cleanepi and Tplyr?

They serve adjacent needs but don't currently overlap on shipped themes. cleanepi and Tplyr 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.

Is cleanepi better than Tplyr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cleanepi and Tplyr 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.

What are the best alternatives to cleanepi?

Top cleanepi alternatives in Analytics are ranked by recent ship velocity. Browse the "cleanepi alternatives" section above for the current picks, or visit /alternatives/cleanepi for the full list with editorial commentary on each.

What are the best alternatives to Tplyr?

Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.