rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A side-by-side editorial comparison of tidytlg and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.
A tables-listings-graphs package that reached CRAN and then went quiet.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
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.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
The visible arc is getting onto CRAN and staying installable — vignette corrections per CRAN comments, a badge, a check fix, and replacing the timber logging package with logrx. The one functional addition is multiple-file support. There has been no release since October 2023, so on this evidence the package is stable or dormant rather than actively developing.
The entries give no signal about planned work; with nothing shipped in roughly two years, the more likely next event is a maintenance release triggered by a dependency or CRAN check than a feature.
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.
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.
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.
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 tidytlg or Tplyr.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
See all tidytlg alternatives → · See all Tplyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — clinical-trials, tables, r-package, pharmaverse — within Analytics. tidytlg 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tidytlg 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.
Top tidytlg alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytlg alternatives" section above for the current picks, or visit /alternatives/tidytlg for the full list with editorial commentary on each.
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.