A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr alternatives
The best Tplyr alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to Tplyr? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, Tplyr shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About 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.
Velocity 0.0 · Last update 57m ago
Top 12 alternatives to Tplyr
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
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.
tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
Geospatial targets grew from two raster helpers into a tiling and multi-backend pipeline layer.
Tplyr vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| Tplyr (baseline) | 0.0 | 0 | clinical-trialstablestraceability | 1.0.0 introduces the traceability metadata framework |
| tidytlg | 0.0 | 0 | clinical-trialstablesr-package | — |
| rlistings | 0.0 | 0 | clinical-trialslistingspagination | — |
| hoardr | 0.0 | 0 | cachingr-packageropensci | — |
| gigs | 0.0 | 0 | growth-standardsneonatal-healthr-package | Conversion API rewritten around data frames and classify_growth() |
| riem | 0.0 | 0 | weather-dataapi-clientr-package | — |
| datasetjson | 0.0 | 0 | clinical-datacdiscjson | Dataset-JSON 1.1.0 support with a redesigned object model |
| ijtiff | 0.0 | 0 | imagingtiffr-package | — |
| tern | 0.0 | 0 | clinical-trialstablesr-package | Two dozen more analysis functions drop make_afun() |
| posteriordb | 0.0 | 0 | bayesianbenchmarkingreference-data | — |
| tinkr | 0.0 | 0 | markdownxmlr-package | First release: the extensible yarn R6 class |
| excluder | 0.0 | 0 | survey-datadata-cleaningr-package | — |
| geotargets | 0.0 | 0 | geospatialpipelinesr-package | stars backend and dynamically branched raster tiles |
The 12 best Tplyr alternatives, in depth
1. tidytlg · velocity 0.0
A tables-listings-graphs package that reached CRAN and then went quiet.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, tidytlg focuses on clinical trials, tables and r package.
tidytlg and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. rlistings · velocity 0.0
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, rlistings focuses on clinical trials, listings and pagination.
rlistings and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. hoardr · velocity 0.0
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, hoardr focuses on caching, r package and ropensci.
hoardr and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. gigs · velocity 0.0
Gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Conversion API rewritten around data frames and classify_growth()”.
Where Tplyr leans on clinical trials, tables and traceability, gigs focuses on growth standards, neonatal health and r package.
gigs and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. riem · velocity 0.0
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, riem focuses on weather data, api client and r package.
riem and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. datasetjson · velocity 0.0
Datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Dataset-JSON 1.1.0 support with a redesigned object model”.
Where Tplyr leans on clinical trials, tables and traceability, datasetjson focuses on clinical data, cdisc and json.
datasetjson and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datasetjson trajectory → · Compare Tplyr vs datasetjson →
7. ijtiff · velocity 0.0
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, ijtiff focuses on imaging, tiff and r package.
ijtiff and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. tern · velocity 0.0
Tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Two dozen more analysis functions drop make_afun()”.
Where Tplyr leans on clinical trials, tables and traceability, tern focuses on clinical trials, tables and r package.
tern and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. posteriordb · velocity 0.0
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, posteriordb focuses on bayesian, benchmarking and reference data.
posteriordb and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full posteriordb trajectory → · Compare Tplyr vs posteriordb →
10. tinkr · velocity 0.0
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “First release: the extensible yarn R6 class”.
Where Tplyr leans on clinical trials, tables and traceability, tinkr focuses on markdown, xml and r package.
tinkr and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. excluder · velocity 0.0
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where Tplyr leans on clinical trials, tables and traceability, excluder focuses on survey data, data cleaning and r package.
excluder and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. geotargets · velocity 0.0
Geospatial targets grew from two raster helpers into a tiling and multi-backend pipeline layer.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “stars backend and dynamically branched raster tiles”.
Where Tplyr leans on clinical trials, tables and traceability, geotargets focuses on geospatial, pipelines and r package.
geotargets and Tplyr have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full geotargets trajectory → · Compare Tplyr vs geotargets →
Frequently asked questions
What are the best alternatives to Tplyr?
The top Tplyr alternatives we currently track in analytics tools are tidytlg, rlistings, hoardr, gigs, riem, ranked by recent ship velocity.
How is this list of Tplyr alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare Tplyr directly with one of these alternatives?
Yes — every card has a "Compare with Tplyr" link to a side-by-side /compare page.