tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of tern and USAboundaries — release velocity, themes, recent moves, and the top alternatives to consider.
tern is migrating its entire analysis-function catalogue off make_afun(), one release at a time.
tern builds the clinical-trial tables, listings, and graphs layer on top of rtables — occurrence counts, survival summaries, ANCOVA, incidence rates, subgroup and biomarker tabulations. The visible work across the window is a systematic refactor: dozens of analysis functions rewritten to drop make_afun() and adopt a common analysis-function style driven by rtables' additional_fun_params. Feature additions ride along with it.
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
tern builds the clinical-trial tables, listings, and graphs layer on top of rtables — occurrence counts, survival summaries, ANCOVA, incidence rates, subgroup and biomarker tabulations. The visible work across the window is a systematic refactor: dozens of analysis functions rewritten to drop make_afun() and adopt a common analysis-function style driven by rtables' additional_fun_params. Feature additions ride along with it.
This is a multi-release architectural migration, not incremental polish. Each release converts another batch of functions, and the count is large — roughly two dozen in the most recent entry alone, after a comparable batch the release before. Alongside it, the denom parameter is being threaded through counting functions and g_lineplot is accumulating layout control, both patterns of standardising arguments that previously varied per function.
The refactor should continue until the make_afun() dependency is gone entirely, with the remaining tabulate_* and biomarker functions the likely next batch; the entries give no date for completion.
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.
The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.
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 tern or USAboundaries.
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 tern alternatives → · See all USAboundaries alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tern and USAboundaries 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. tern and USAboundaries 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 tern alternatives in Analytics are ranked by recent ship velocity. Browse the "tern alternatives" section above for the current picks, or visit /alternatives/tern for the full list with editorial commentary on each.
Top USAboundaries alternatives in Analytics are ranked by recent ship velocity. Browse the "USAboundaries alternatives" section above for the current picks, or visit /alternatives/usaboundaries for the full list with editorial commentary on each.