← Back to home
Comparison · Analytics

crul vs tidymodels

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

crul vs tidymodels: at a glance

Featurecrultidymodels
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropenscitidymodels, meta-package, dependency-management, namespace-conflicts
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 tidymodels?

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

Read the full tidymodels trajectory →

crul vs tidymodels: 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.

T
tidymodels
ANALYTICS
0.0

The meta-package ships almost nothing, which is exactly what a version-pinning shim should do

◆ Current state

The tidymodels package is a loader and version pin for the modeling framework's core set rather than a place where features live. Its entire changelog consists of updated dependency versions, adjustments to how tidymodels_prefer() resolves name conflicts against other packages, and the occasional addition of a package to the core set — workflowsets in 0.1.3, tailor in 1.4.0. The most recent releases moved the package's own code from the magrittr pipe to R's base pipe and patched a bug where some attached packages were omitted.

◆ Where it's heading

Release cadence tracks the ecosystem rather than any roadmap of its own: a version bump when member packages release, a tidymodels_prefer() rule when a new conflict appears — DALEX::explains() over dplyr::explains(), recipes::update() over other update() methods. Additions to the core set are the only structurally interesting events, and there have been two in seven releases. Everything else is plumbing that exists so a single library() call attaches a consistent set of versions.

◆ Prediction

The next release will most likely be another version-set update, with any new core package the only thing worth noting. Feature news for this framework will keep arriving in the member packages, not here.

Alternatives to crul and tidymodels

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 tidymodels.

See all crul alternatives → · See all tidymodels alternatives →

Recent activity from crul and tidymodels

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

  1. 11mo agotidymodelsFix for packages omitted from attachment
  2. 11mo agotidymodelstailor joins the core set; base pipe replaces magrittr
  3. 1y agocrulMocking becomes a client parameter, independent of webmockr
  4. 1y agotidymodelsConflict preferences added for DALEX and recipes
  5. 2y agocrulAsync requests become mockable through webmockr
  6. 2y agocrulDocumentation fixes and test helper tweak
  7. 3y agocrulHTTP retries reach the async classes
  8. 3y agotidymodelsConflict preferences and pinned versions refreshed
  9. 3y agocrulClearer error for mismatched urls and disk lengths
  10. 4y agotidymodelsVersion refresh and testthat 3e migration
  11. 4y agocrulAsyncQueue gains response accessors; results print as a summary
  12. 4y agotidymodelsRotating startup messages and an analysis template

Frequently asked questions

What is the difference between crul and tidymodels?

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

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

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