metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of logrx and teal.modules.clinical — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Roche's clinical teal modules have settled into slow, decorator-driven maintenance.
The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.
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.
The module library took its architectural break in 0.9.0, when every module moved to teal_data objects and dropped data_extract_spec inputs. Work since then is narrower: formatting arguments, decorator plumbing, and per-module bug fixes. The 0.13.0 candidates cut in July 2026 are a two-tag same-day release where the first tag carries all the notes.
Development has shifted from reshaping the module API to making outputs configurable — numeric formatting in tm_t_summary, several decorators applied to one output object, categorical statistics in summary_by. Changes arrive from a wide bench of Roche engineers with occasional outside contributors, and releases go through candidates rather than straight to final.
A 0.13.0 final should follow the candidates with little beyond a dependency bump; the decorator work ported from teal.modules.general is the most likely source of the next batch of changes.
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 logrx or teal.modules.clinical.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all logrx alternatives → · See all teal.modules.clinical alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — clinical-trials — within Analytics. logrx and teal.modules.clinical 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. logrx and teal.modules.clinical 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 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.
Top teal.modules.clinical alternatives in Analytics are ranked by recent ship velocity. Browse the "teal.modules.clinical alternatives" section above for the current picks, or visit /alternatives/teal-modules-clinical for the full list with editorial commentary on each.