tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of gigs and logrx — release velocity, themes, recent moves, and the top alternatives to consider.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.
With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.
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 gigs or logrx.
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.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gigs and logrx 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. gigs and logrx 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 gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.
Top logrx alternatives in Analytics are ranked by recent ship velocity. Browse the "logrx alternatives" section above for the current picks, or visit /alternatives/logrx for the full list with editorial commentary on each.