tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of gigs and S7 — 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.
S7 has stopped adding surface and started proving it holds up against R itself.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
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.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
The changelog is thinning by design — 0.1.0 was a months-long feature dump, 0.2.0 a coordinated architectural revision, 0.2.2 a single line about internal R-devel support. That shape usually means an API the maintainers consider settled, where the remaining work is tracking the host language rather than extending the system. The one recurring theme is validation cost: repeated releases have made validation less frequent, more targeted, or skippable outright.
Expect continued small releases pinned to R-devel changes rather than new class-system features, with any further movement most likely in the validation and property-setter path that the last two feature changes both touched.
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 S7.
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.
They serve adjacent needs but don't currently overlap on shipped themes. gigs and S7 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 S7 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 S7 alternatives in Analytics are ranked by recent ship velocity. Browse the "S7 alternatives" section above for the current picks, or visit /alternatives/s7 for the full list with editorial commentary on each.