tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of admiralonco and chattr — release velocity, themes, recent moves, and the top alternatives to consider.
The oncology ADaM helper is dissolving into admiral core, one deprecation at a time.
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
The package is converging on a documentation-and-templates model: reusable derivation logic moves upstream into admiral, and admiralonco keeps only the oncology-specific know-how. Every release since 1.0.0 has added a criteria vignette rather than new exported functions, and 1.4.1 extends that by making the template set browsable from the Get Started menu. The surface users program against is shrinking while the guidance they read is growing.
Expect the deprecation cycle started in 1.4.0 to advance through its warning and error phases across the next one or two releases, with new work arriving as another response-criteria vignette rather than new functions.
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
The first two releases show why that happened. Each provider brought its own error formats, token discovery and response handling, and 0.2.0 is largely a list of per-provider repairs — OpenAI error parsing, Copilot token discovery and model defaults, a new Databricks foundation model backend. Maintaining that surface scales linearly with the number of providers, and the pivot to ellmer trades it for a single dependency. The cost shows up immediately in 0.3.1, which exists solely to absorb a change in ellmer's token object.
Expect chattr's releases to now track ellmer's, as 0.3.1 already does, with the package's own work concentrating on the IDE experience rather than model connectivity. New provider support will arrive without a chattr release at all.
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 admiralonco or chattr.
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 admiralonco alternatives → · See all chattr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. admiralonco and chattr 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. admiralonco and chattr 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 admiralonco alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralonco alternatives" section above for the current picks, or visit /alternatives/admiralonco for the full list with editorial commentary on each.
Top chattr alternatives in Analytics are ranked by recent ship velocity. Browse the "chattr alternatives" section above for the current picks, or visit /alternatives/chattr for the full list with editorial commentary on each.