← Back to analytics tools
Alternatives · analytics tools

admiralonco alternatives

The best admiralonco alternatives in analytics tools, ranked by Sparkpulse's velocity_score.

Updated Aug 14, 2026

Looking for the best alternatives to admiralonco? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, admiralonco shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.

About admiralonco

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.

Velocity 0.0 · Last update 55m ago

Read the full admiralonco trajectory →

Top 12 alternatives to admiralonco

Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.

Browse all analytics tools products →

admiralonco vs alternatives — shipping velocity at a glance

Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.

ProductVelocitySparks · 30dFocus areasLatest release
admiralonco (baseline)0.00oncologyadampharmaversePSA endpoints land as function deprecation begins
mirai2.50parallel-computingasyncbackpressureDispatcher becomes a thread, and the queue gains a memory budget
ggsurvfit2.50survival-analysisggplot2competing-risks
nanonext2.50async-messagingnnghttp-serverZero-copy message forwarding, and cmake dropped from the build
DataSpaceR2.50hiv-researchimmunology-dataapi-clientQuery API rebuilt and DAASH antibody sequence access added
metatools0.00pharmaversesdtmadam
marquee0.00r-libtypographymarkdown
logrx0.00pharmaverseloggingclinical-trials
lobstr0.00r-libintrospectionmemorytruelength reporting dropped for public C API compliance
GSODR0.00ropensciweather-datar-package
giscoR0.00eurostatgeospatialropensci1.0 caches the dataset index so new vintages need no release
FedData0.00ropenscigeospatialr-packagesp and raster dropped; everything returns terra or sf
EDIutils0.00ropenscir-packageapi-clientEDI-IDs replace Distinguished Names as authentication moves to IAM

The 12 best admiralonco alternatives, in depth

1. mirai · velocity 2.5

Mirai removed its dispatcher process and added memory backpressure to the queue.

Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Dispatcher becomes a thread, and the queue gains a memory budget”.

Where admiralonco leans on oncology, adam and pharmaverse, mirai focuses on parallel computing, async and backpressure.

mirai and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

2. ggsurvfit · velocity 2.5

Ggsurvfit is in correctness-and-compatibility mode, not feature mode.

Its velocity score of 2.5/10 reflects longer-term release cadence.

Where admiralonco leans on oncology, adam and pharmaverse, ggsurvfit focuses on survival analysis, ggplot2 and competing risks.

ggsurvfit and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

3. nanonext · velocity 2.5

Nanonext keeps shrinking its build requirements while adding messaging primitives.

Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Zero-copy message forwarding, and cmake dropped from the build”.

Where admiralonco leans on oncology, adam and pharmaverse, nanonext focuses on async messaging, nng and http server.

nanonext and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

4. DataSpaceR · velocity 2.5

DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.

Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “Query API rebuilt and DAASH antibody sequence access added”.

Where admiralonco leans on oncology, adam and pharmaverse, DataSpaceR focuses on hiv research, immunology data and api client.

DataSpaceR and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

5. metatools · velocity 0.0

SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where admiralonco leans on oncology, adam and pharmaverse, metatools focuses on pharmaverse, sdtm and adam.

metatools and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

6. marquee · velocity 0.0

Marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where admiralonco leans on oncology, adam and pharmaverse, marquee focuses on r lib, typography and markdown.

marquee and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

7. logrx · velocity 0.0

A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where admiralonco leans on oncology, adam and pharmaverse, logrx focuses on pharmaverse, logging and clinical trials.

logrx and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

8. lobstr · velocity 0.0

R's object inspector is losing its view of the internals as CRAN closes off the private C API.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “truelength reporting dropped for public C API compliance”.

Where admiralonco leans on oncology, adam and pharmaverse, lobstr focuses on r lib, introspection and memory.

lobstr and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

9. GSODR · velocity 0.0

A weather-station data client that broke one return type to hand back distances instead of bare IDs.

Its velocity score of 0.0/10 reflects longer-term release cadence.

Where admiralonco leans on oncology, adam and pharmaverse, GSODR focuses on ropensci, weather data and r package.

GSODR and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

10. giscoR · velocity 0.0

GiscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0 caches the dataset index so new vintages need no release”.

Where admiralonco leans on oncology, adam and pharmaverse, giscoR focuses on eurostat, geospatial and ropensci.

giscoR and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

11. FedData · velocity 0.0

FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “sp and raster dropped; everything returns terra or sf”.

Where admiralonco leans on oncology, adam and pharmaverse, FedData focuses on ropensci, geospatial and r package.

FedData and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

12. EDIutils · velocity 0.0

The EDI data client is being dragged through its repository's identity-system migration.

Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “EDI-IDs replace Distinguished Names as authentication moves to IAM”.

Where admiralonco leans on oncology, adam and pharmaverse, EDIutils focuses on ropensci, r package and api client.

EDIutils and admiralonco have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.

Frequently asked questions

What are the best alternatives to admiralonco?

The top admiralonco alternatives we currently track in analytics tools are mirai, ggsurvfit, nanonext, DataSpaceR, metatools, ranked by recent ship velocity.

How is this list of admiralonco alternatives ranked?

Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.

Can I compare admiralonco directly with one of these alternatives?

Yes — every card has a "Compare with admiralonco" link to a side-by-side /compare page.