marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A side-by-side editorial comparison of admiraldev and metatools — release velocity, themes, recent moves, and the top alternatives to consider.
The admiral family's toolbox package keeps absorbing infrastructure the main package used to carry.
admiraldev is the developer-facing utility layer beneath the {admiral} clinical-programming family: assertions, custom roxygen roclets, linter configuration and deprecation helpers. Recent releases have pulled shared machinery out of {admiral} itself, most recently the roxygen helper functions in 1.5.0. Its users are other package authors, not clinical programmers.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
admiraldev is the developer-facing utility layer beneath the {admiral} clinical-programming family: assertions, custom roxygen roclets, linter configuration and deprecation helpers. Recent releases have pulled shared machinery out of {admiral} itself, most recently the roxygen helper functions in 1.5.0. Its users are other package authors, not clinical programmers.
The arc is consolidation — each release moves one more piece of cross-package tooling into a single place and tightens the standards it enforces. 1.4.0 added an admiral_linters() configuration mandating cli::cli_abort() over stop() across the family, and 1.1.0 had already migrated the assertion layer to {cli} messaging. Breaking changes are routine here and are managed through an explicit four-phase deprecation process.
Expect further extraction of shared helpers from {admiral} into this package, and continued roxygen2 8.0.0 follow-through in the documentation tooling.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
The package's development has been concentrated on one function, combine_supp(), which is where the messy realities of supplemental qualifiers surface — whitespace in join keys, empty supp datasets, colliding names. 0.1.6 also drew three first-time contributors, which is the healthiest signal in the history, but no release has followed. Sibling packages have meanwhile been dropping metatools as a dependency.
Without a release in two years the package looks stable rather than active; the plausible trigger is a controlled-terminology or dplyr change that forces the checks to be updated.
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 admiraldev or metatools.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all admiraldev alternatives → · See all metatools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — pharmaverse — within Analytics. admiraldev and metatools 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. admiraldev and metatools 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 admiraldev alternatives in Analytics are ranked by recent ship velocity. Browse the "admiraldev alternatives" section above for the current picks, or visit /alternatives/admiraldev for the full list with editorial commentary on each.
Top metatools alternatives in Analytics are ranked by recent ship velocity. Browse the "metatools alternatives" section above for the current picks, or visit /alternatives/metatools for the full list with editorial commentary on each.