tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
tidymodels vs webmockr
A side-by-side editorial comparison of tidymodels and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
tidymodels vs webmockr: at a glance
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.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
tidymodels vs webmockr: editorial side-by-side
tidymodels
0.0ANALYTICS
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.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to tidymodels and webmockr
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 tidymodels or webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all tidymodels alternatives → · See all webmockr alternatives →
Recent activity from tidymodels and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agotidymodelsFix for packages omitted from attachment
- 11mo agotidymodelstailor joins the core set; base pipe replaces magrittr
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agotidymodelsConflict preferences added for DALEX and recipes
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 3y agotidymodelsConflict preferences and pinned versions refreshed
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
- 4y agotidymodelsVersion refresh and testthat 3e migration
- 4y agotidymodelsRotating startup messages and an analysis template
Frequently asked questions
What is the difference between tidymodels and webmockr?
They serve adjacent needs but don't currently overlap on shipped themes. tidymodels and webmockr 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 tidymodels better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tidymodels and webmockr 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 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.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.