Adding chemical databases with one hand while public ones close programmatic access with the other.
sdtm.oak alternatives
The best sdtm.oak alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to sdtm.oak? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, sdtm.oak 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 sdtm.oak
Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.
sdtm.oak builds SDTM datasets — the tabulation standard clinical trial submissions are filed in — from raw collected data. The 0.1.0 release shipped the mapping algorithm functions and derived-variable helpers but explicitly excluded DM, trial design domains, and several others. Version 0.2.0 closes the largest of those gaps, adding DM domain support via calc_min_max_date() and oak_calc_ref_dates(), plus generate_sdtm_supp() for supplemental qualifier domains.
Velocity 0.0 · Last update 50m ago
Top 12 alternatives to sdtm.oak
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
Reorganised its parsers by vendor, then opened the parser slot to users.
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
sdtm.oak 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 |
|---|---|---|---|---|
| sdtm.oak (baseline) | 0.0 | 0 | clinical-trialssdtmpharmaverse | sdtm.oak v0.2.0 CRAN release |
| webchem | 0.0 | 0 | cheminformaticsweb-apisdata-access | ChemIDplus and PAN queries removed as sources shut down |
| sftime | 0.0 | 0 | spatiotemporalr-spatialinteroperability | — |
| ReLTER | 0.0 | 0 | ecologyresearch-infrastructureropensci | ReLTER v1.0.0 |
| waywiser | 0.0 | 0 | spatial-statisticsmodel-assessmenttidymodels | — |
| taxizedb | 0.0 | 0 | taxonomybiodiversity-datasqlite | SQLite everywhere, three new sources, taxize verbs ported |
| fellingdater | 0.0 | 0 | dendrochronologycrossdatingarchaeology | Adds a full crossdating and tree-ring analysis toolkit |
| textshaping | 0.0 | 0 | typographytext-shapingbidi | Shaping engine rewritten to honour global text direction |
| vcr | 0.0 | 0 | testinghttp-mockingbreaking-change | 2.0 removes the logging API and the exported R6 classes |
| parzer | 0.0 | 0 | geospatialstring-parsingcoordinates | — |
| dfms | 0.0 | 0 | nowcastingstate-space-modelseconometrics | 1.0: rOpenSci review passed, news decomposition added |
| lightr | 0.0 | 0 | spectrometryfile-parsersbreaking-change | Parsers renamed by vendor; Avantes binary support restored |
| sass | 0.0 | 0 | csssassr-package | — |
The 12 best sdtm.oak alternatives, in depth
1. webchem · velocity 0.0
Adding chemical databases with one hand while public ones close programmatic access with the other.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “ChemIDplus and PAN queries removed as sources shut down”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, webchem focuses on cheminformatics, web apis and data access.
webchem and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. sftime · velocity 0.0
The spatiotemporal companion to sf, moving at the pace of the packages around it.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, sftime focuses on spatiotemporal, r spatial and interoperability.
sftime and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. ReLTER · velocity 0.0
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “ReLTER v1.0.0”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, ReLTER focuses on ecology, research infrastructure and ropensci.
ReLTER and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. waywiser · velocity 0.0
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, waywiser focuses on spatial statistics, model assessment and tidymodels.
waywiser and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. taxizedb · velocity 0.0
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “SQLite everywhere, three new sources, taxize verbs ported”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, taxizedb focuses on taxonomy, biodiversity data and sqlite.
taxizedb and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. fellingdater · velocity 0.0
Went from estimating felling dates to doing the crossdating that produces them.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Adds a full crossdating and tree-ring analysis toolkit”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, fellingdater focuses on dendrochronology, crossdating and archaeology.
fellingdater and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full fellingdater trajectory → · Compare sdtm.oak vs fellingdater →
7. textshaping · velocity 0.0
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Shaping engine rewritten to honour global text direction”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, textshaping focuses on typography, text shaping and bidi.
textshaping and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full textshaping trajectory → · Compare sdtm.oak vs textshaping →
8. vcr · velocity 0.0
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “2.0 removes the logging API and the exported R6 classes”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, vcr focuses on testing, http mocking and breaking change.
vcr and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. parzer · velocity 0.0
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, parzer focuses on geospatial, string parsing and coordinates.
parzer and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. dfms · velocity 0.0
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0: rOpenSci review passed, news decomposition added”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, dfms focuses on nowcasting, state space models and econometrics.
dfms and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. lightr · velocity 0.0
Reorganised its parsers by vendor, then opened the parser slot to users.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Parsers renamed by vendor; Avantes binary support restored”.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, lightr focuses on spectrometry, file parsers and breaking change.
lightr and sdtm.oak have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. sass · velocity 0.0
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sdtm.oak leans on clinical trials, sdtm and pharmaverse, sass focuses on css, sass and r package.
sass and sdtm.oak 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 sdtm.oak?
The top sdtm.oak alternatives we currently track in analytics tools are webchem, sftime, ReLTER, waywiser, taxizedb, ranked by recent ship velocity.
How is this list of sdtm.oak alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare sdtm.oak directly with one of these alternatives?
Yes — every card has a "Compare with sdtm.oak" link to a side-by-side /compare page.