tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of c3dr and rlistings — release velocity, themes, recent moves, and the top alternatives to consider.
A biomechanics C3D reader graduated through rOpenSci review to CRAN, then learned to write force plates.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
The package is filling in the write side of the read/write pair. Reading was in place from the start; 0.2.0 extends c3d_write() to force-platform data on a direct user request, and the accompanying work preserves matrix structure on import and tracks upstream EZC3D changes. The review-era releases hardened validation and error messages, so the current cycle can be spent on capability rather than polish.
Expect further coverage of C3D block types in the writer and continued tracking of EZC3D releases; the changelog gives no signal of analysis features beyond file I/O.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
The package is progressively delegating pagination to formatters rather than implementing it — paginate_listing() was refactored to call formatters' paginate_to_mpfs() directly, and truetype font support arrived through a new formatters API. That reduces duplicated logic but ties the package's page-break behaviour to a dependency it shares with rtables. Feature work beyond pagination is thin: better error messages for unsupported column classes, a cheatsheet.
Expect pagination fidelity to remain the focus, with changes arriving as formatters exposes more of its layout machinery rather than as rlistings-native features.
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 c3dr or rlistings.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
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.
See all c3dr alternatives → · See all rlistings alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. c3dr and rlistings 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. c3dr and rlistings 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 c3dr alternatives in Analytics are ranked by recent ship velocity. Browse the "c3dr alternatives" section above for the current picks, or visit /alternatives/c3dr for the full list with editorial commentary on each.
Top rlistings alternatives in Analytics are ranked by recent ship velocity. Browse the "rlistings alternatives" section above for the current picks, or visit /alternatives/rlistings for the full list with editorial commentary on each.