Tplyr
Tplyr made clinical summary tables explain where every number came from.
A side-by-side editorial comparison of textreuse and tidytlg — release velocity, themes, recent moves, and the top alternatives to consider.
A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
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.
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
The arc here is restoration rather than expansion. The work has gone into making the package survivable — silencing deprecated dplyr and tidyr selection and many-to-many join warnings, moving from dead Travis and AppVeyor configs to GitHub Actions, and validating across five R platform and version combinations. Release notes now lead with verification evidence rather than features, which is the signature of a maintainer stabilizing an inherited codebase.
Expect continued compatibility releases tracking tidyverse deprecations; nothing in these entries indicates new hashing or alignment capability is planned.
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.
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 textreuse or tidytlg.
Tplyr made clinical summary tables explain where every number came from.
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.
See all textreuse alternatives → · See all tidytlg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, maintenance — within Analytics. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top textreuse alternatives in Analytics are ranked by recent ship velocity. Browse the "textreuse alternatives" section above for the current picks, or visit /alternatives/textreuse for the full list with editorial commentary on each.
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.