← Back to home
Comparison · Analytics

crul vs DoseFinding

A side-by-side editorial comparison of crul and DoseFinding — release velocity, themes, recent moves, and the top alternatives to consider.

crul vs DoseFinding: at a glance

FeaturecrulDoseFinding
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropenscidose-response, mcp-mod, clinical-trials, model-averaging
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is DoseFinding?

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

Read the full DoseFinding trajectory →

crul vs DoseFinding: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

D
DoseFinding
ANALYTICS
0.0

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

◆ Current state

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

◆ Where it's heading

The pattern before the handover was maintenance — R-devel compliance, a bug fix, a link. After it, each release carries a named methodological addition with an acknowledged contributor, plus documentation to match: a longitudinal analysis vignette shipped alongside the interim power work. Housekeeping continues underneath, mostly clearing deprecated ggplot2 interfaces, aes_string in one release and qplot in the next.

◆ Prediction

Given the last two releases each added one method with a supporting vignette, expect the next to follow the same shape. Both additions so far extend the package beyond fixed dose-response fitting, so adaptive and interim methodology is the more likely direction.

Alternatives to crul and DoseFinding

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 crul or DoseFinding.

See all crul alternatives → · See all DoseFinding alternatives →

Recent activity from crul and DoseFinding

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1y agocrulMocking becomes a client parameter, independent of webmockr
  2. 1y agoDoseFindingConditional and predictive power for interim analyses
  3. 1y agoDoseFindingModel averaging arrives for dose-response fitting
  4. 1y agoDoseFindingPackage moves to openpharma under new maintainership
  5. 2y agocrulAsync requests become mockable through webmockr
  6. 2y agocrulDocumentation fixes and test helper tweak
  7. 2y agoDoseFindingCompliance update for R-devel
  8. 3y agoDoseFindingpowMCTBinCount bug fix
  9. 3y agocrulHTTP retries reach the async classes
  10. 3y agocrulClearer error for mismatched urls and disk lengths
  11. 4y agocrulAsyncQueue gains response accessors; results print as a summary

Frequently asked questions

What is the difference between crul and DoseFinding?

They serve adjacent needs but don't currently overlap on shipped themes. crul and DoseFinding 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 crul better than DoseFinding?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul and DoseFinding 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 crul?

Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.

What are the best alternatives to DoseFinding?

Top DoseFinding alternatives in Analytics are ranked by recent ship velocity. Browse the "DoseFinding alternatives" section above for the current picks, or visit /alternatives/dosefinding for the full list with editorial commentary on each.