datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
sdtm.oak vs vcr
A side-by-side editorial comparison of sdtm.oak and vcr — release velocity, themes, recent moves, and the top alternatives to consider.
sdtm.oak vs vcr: at a glance
What is 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.
What is vcr?
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.
sdtm.oak vs vcr: editorial side-by-side
sdtm.oak
0.0ANALYTICS
Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.
◆ Current state
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.
◆ Where it's heading
This is the pharmaverse pattern of building submission tooling in the open, one domain class at a time, with the release history running through GitHub release-candidate tags before each CRAN submission. The direction is clear from the domain checklist: start with the mechanically simple Findings and Events domains, then work toward the ones with cross-dataset dependencies. DM and SUPP were the two that most often forced teams back to bespoke code.
◆ Prediction
The remaining exclusions from the 0.1.0 scope — trial design domains, SV, SE, RELREC and the EPOCH variable — are the obvious next targets, with EPOCH likely first since it depends on the reference dates 0.2.0 just added. Expect the same rhythm of release candidates ahead of each CRAN submission.
vcr
0.0ANALYTICS
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
◆ Current state
vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.
◆ Where it's heading
The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.
◆ Prediction
Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.
Alternatives to sdtm.oak and vcr
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 sdtm.oak or vcr.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all sdtm.oak alternatives → · See all vcr alternatives →
Recent activity from sdtm.oak and vcr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agovcr2.0 removes the logging API and the exported R6 classes ⚡
- 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release ⚡
- 1y agovcrMaintainer email address updated
- 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
- 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
- 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
- 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
- 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)
- 2y agovcrAdds httr2 support alongside httr and crul ⚡
- 3y agovcrDrops compilation; test setup moves back to helper files
- 3y agovcrFixes request matching with escaped characters
- 5y agovcrvcr_test_path() finds the package root correctly
Frequently asked questions
What is the difference between sdtm.oak and vcr?
They serve adjacent needs but don't currently overlap on shipped themes. sdtm.oak and vcr 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.
Is sdtm.oak better than vcr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sdtm.oak and vcr 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.
What are the best alternatives to sdtm.oak?
Top sdtm.oak alternatives in Analytics are ranked by recent ship velocity. Browse the "sdtm.oak alternatives" section above for the current picks, or visit /alternatives/sdtm-oak for the full list with editorial commentary on each.
What are the best alternatives to vcr?
Top vcr alternatives in Analytics are ranked by recent ship velocity. Browse the "vcr alternatives" section above for the current picks, or visit /alternatives/vcr for the full list with editorial commentary on each.