r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of admiralonco and ymlthis — 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.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
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.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.
Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.
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 ymlthis.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all admiralonco alternatives → · See all ymlthis 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 ymlthis 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 ymlthis 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 ymlthis alternatives in Analytics are ranked by recent ship velocity. Browse the "ymlthis alternatives" section above for the current picks, or visit /alternatives/ymlthis for the full list with editorial commentary on each.