metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of ggsurvfit and logrx — release velocity, themes, recent moves, and the top alternatives to consider.
ggsurvfit is in correctness-and-compatibility mode, not feature mode.
The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.
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.
The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.
The feature surface settled around 1.0.0, when risk-table alignment was exported and colour and linetype defaults became configurable. Since then the work is keeping pace with survival, ggplot2 and tidycmprsk changes, and closing cases where the plotted curve and the annotation disagreed — the p-value matched by position rather than name, confidence limits swapped for multi-state models, quantiles read off a plateau.
Expect the next release to track upstream survival or ggplot2 changes rather than add plotting features; the CDISC censoring convention adopted in Surv_CNSR() suggests further alignment with clinical data standards is the likelier direction.
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 ggsurvfit or logrx.
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 ggsurvfit alternatives → · See all logrx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggsurvfit 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. ggsurvfit 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 ggsurvfit alternatives in Analytics are ranked by recent ship velocity. Browse the "ggsurvfit alternatives" section above for the current picks, or visit /alternatives/ggsurvfit 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.