The stubbing library added httr2 support, then spent a year cutting itself free of everything else
pharmaverseadam alternatives
The best pharmaverseadam alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to pharmaverseadam? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, pharmaverseadam 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 pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to pharmaverseadam
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
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
Six years since the last functional change, and Google renamed the service it wraps in the release before that
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
One document API over six databases, and every release is spent absorbing their JSON engines' churn
Sparse vectors stopped being a storage trick and became something you can do arithmetic on
pharmaverseadam 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.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| pharmaverseadam (baseline) | 0.0 | 0 | pharmaverseclinical-dataadam | — |
| webmockr | 0.0 | 0 | http-mockingtestinghttr2 | httr2 joins httr and crul as a supported client |
| crul | 0.0 | 0 | http-clientasyncmocking | Mocking becomes a client parameter, independent of webmockr |
| dendroNetwork | 0.0 | 0 | dendrochronologynetwork-analysiscytoscape | — |
| chattr | 0.0 | 0 | llmrstudioide-integration | All model integration moves to ellmer, direct backends removed |
| cloudml | 0.0 | 0 | machine-learninggoogle-cloudtensorflow | — |
| tidymodels | 0.0 | 0 | tidymodelsmeta-packagedependency-management | — |
| datapack | 0.0 | 0 | research-datadataoneprovenance | Assembled data packages become editable in place |
| USAboundaries | 0.0 | 0 | geospatialcensus-datasf | Data split into a companion package; all boundaries become sf |
| slider | 0.0 | 0 | sliding-windowstidyversec-api-compliance | — |
| simtrial | 0.0 | 0 | clinical-trialsgroup-sequentialsurvival-analysis | RMST and milestone tests, plus a user-definable cut and test framework |
| nodbi | 0.0 | 0 | document-databasesjsonduckdb | Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres |
| sparsevctrs | 0.0 | 0 | sparse-datatidymodelsaltrep | Scalar and element-wise arithmetic for sparse vectors |
The 12 best pharmaverseadam alternatives, in depth
1. webmockr · velocity 0.0
The stubbing library added httr2 support, then spent a year cutting itself free of everything else.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “httr2 joins httr and crul as a supported client”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, webmockr focuses on http mocking, testing and httr2.
webmockr and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full webmockr trajectory → · Compare pharmaverseadam vs webmockr →
2. crul · velocity 0.0
Crul took mocking back from webmockr and made it a property of the client itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Mocking becomes a client parameter, independent of webmockr”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, crul focuses on http client, async and mocking.
crul and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. dendroNetwork · velocity 0.0
Six releases, six identical bodies — the feed carries the package abstract instead of release notes.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, dendroNetwork focuses on dendrochronology, network analysis and cytoscape.
dendroNetwork and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full dendroNetwork trajectory → · Compare pharmaverseadam vs dendroNetwork →
4. chattr · velocity 0.0
Chattr deleted every LLM integration it had written and outsourced the lot to ellmer.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “All model integration moves to ellmer, direct backends removed”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, chattr focuses on llm, rstudio and ide integration.
chattr and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full chattr trajectory → · Compare pharmaverseadam vs chattr →
5. cloudml · velocity 0.0
Six years since the last functional change, and Google renamed the service it wraps in the release before that.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, cloudml focuses on machine learning, google cloud and tensorflow.
cloudml and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full cloudml trajectory → · Compare pharmaverseadam vs cloudml →
6. tidymodels · velocity 0.0
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, tidymodels focuses on tidymodels, meta package and dependency management.
tidymodels and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full tidymodels trajectory → · Compare pharmaverseadam vs tidymodels →
7. datapack · velocity 0.0
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Assembled data packages become editable in place”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, datapack focuses on research data, dataone and provenance.
datapack and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datapack trajectory → · Compare pharmaverseadam vs datapack →
8. USAboundaries · velocity 0.0
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Data split into a companion package; all boundaries become sf”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, USAboundaries focuses on geospatial, census data and sf.
USAboundaries and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full USAboundaries trajectory → · Compare pharmaverseadam vs USAboundaries →
9. slider · velocity 0.0
Feature-complete since 2021, and every release since has been paying CRAN's C API bill.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, slider focuses on sliding windows, tidyverse and c api compliance.
slider and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full slider trajectory → · Compare pharmaverseadam vs slider →
10. simtrial · velocity 0.0
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “RMST and milestone tests, plus a user-definable cut and test framework”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, simtrial focuses on clinical trials, group sequential and survival analysis.
simtrial and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full simtrial trajectory → · Compare pharmaverseadam vs simtrial →
11. nodbi · velocity 0.0
One document API over six databases, and every release is spent absorbing their JSON engines' churn.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, nodbi focuses on document databases, json and duckdb.
nodbi and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full nodbi trajectory → · Compare pharmaverseadam vs nodbi →
12. sparsevctrs · velocity 0.0
Sparse vectors stopped being a storage trick and became something you can do arithmetic on.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Scalar and element-wise arithmetic for sparse vectors”.
Where pharmaverseadam leans on pharmaverse, clinical data and adam, sparsevctrs focuses on sparse data, tidymodels and altrep.
sparsevctrs and pharmaverseadam have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full sparsevctrs trajectory → · Compare pharmaverseadam vs sparsevctrs →
Frequently asked questions
What are the best alternatives to pharmaverseadam?
The top pharmaverseadam alternatives we currently track in analytics tools are webmockr, crul, dendroNetwork, chattr, cloudml, ranked by recent ship velocity.
How is this list of pharmaverseadam alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare pharmaverseadam directly with one of these alternatives?
Yes — every card has a "Compare with pharmaverseadam" link to a side-by-side /compare page.