tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of r2rtf and webchem — release velocity, themes, recent moves, and the top alternatives to consider.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
Adding chemical databases with one hand while public ones close programmatic access with the other.
webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
Two threads run through the window. One is output reach: RTF remains the composition target, but the artifacts that come out of it now include DOCX and HTML, and page numbering can be made table-relative across multi-page tables. The other is durability under a moving R and font stack — the ANSI/Unicode converter was rebuilt, the LaTeX mapping table generated from code rather than shipped as sysdata, unlist() usage fixed for R 4.5, and graphics-device leaks that produced stray Rplots.pdf closed off.
Having exported DOCX and HTML conversion, the likely next step is filling in what those formats lose relative to RTF — pagination and footnote fidelity are the obvious gaps. The i18n path currently covers Chinese only, so additional font families are the other plausible direction.
webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.
Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.
Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.
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 r2rtf or webchem.
A tables-listings-graphs package that reached CRAN and then went quiet.
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.
See all r2rtf alternatives → · See all webchem alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. r2rtf and webchem 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. r2rtf and webchem 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 r2rtf alternatives in Analytics are ranked by recent ship velocity. Browse the "r2rtf alternatives" section above for the current picks, or visit /alternatives/r2rtf for the full list with editorial commentary on each.
Top webchem alternatives in Analytics are ranked by recent ship velocity. Browse the "webchem alternatives" section above for the current picks, or visit /alternatives/webchem for the full list with editorial commentary on each.