tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of datasetjson and gMCPLite — release velocity, themes, recent moves, and the top alternatives to consider.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
The package's roadmap is not its own — it tracks a CDISC standard that is still moving, and 0.3.0 is what happens when the standard revises: object model, read and write paths, and JSON backend all changed together. Performance was addressed in the same pass, which matters because submission datasets are large enough that a slow serialiser is a real constraint.
The next significant release will most likely follow the next Dataset-JSON schema revision rather than an internal roadmap, given that 0.3.0 was driven entirely by the 1.1.0 update.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
This is a package with a fixed job. The maintainers track two moving targets — the upstream gMCP it forked from, and the R graphics and testing stack underneath it — and pull across only what is needed. The addition of vdiffr visual regression tests for `hGraph()` is the most substantive recent change and fits the same posture: the plots are the deliverable, so pin them against accidental drift rather than redesign them.
Expect the pattern to continue — compatibility releases driven by ggplot2, testthat and pkgdown changes, with any statistical content arriving only as a selective port from upstream gMCP.
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 datasetjson or gMCPLite.
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 datasetjson alternatives → · See all gMCPLite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. datasetjson and gMCPLite 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. datasetjson and gMCPLite 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 datasetjson alternatives in Analytics are ranked by recent ship velocity. Browse the "datasetjson alternatives" section above for the current picks, or visit /alternatives/datasetjson for the full list with editorial commentary on each.
Top gMCPLite alternatives in Analytics are ranked by recent ship velocity. Browse the "gMCPLite alternatives" section above for the current picks, or visit /alternatives/gmcplite for the full list with editorial commentary on each.