tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
serofoi vs webmockr
A side-by-side editorial comparison of serofoi and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
serofoi vs webmockr: at a glance
What is serofoi?
serofoi grew a serosurvey simulator alongside the force-of-infection models it was built to fit.
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
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.
serofoi vs webmockr: editorial side-by-side
serofoi
0.0ANALYTICS
serofoi grew a serosurvey simulator alongside the force-of-infection models it was built to fit.
◆ Current state
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
◆ Where it's heading
The package moved from fitting-only to a fit-and-simulate pair. 0.1.0 added simulation from time- or age-varying force-of-infection trends and simplified the fitted object down to a Stan fit; 1.0.2 broadened simulation into full serosurvey generation with its own vignette. 1.0.3 then spent its effort on naming consistency and plotting options, which is what a package does once its scope is set.
◆ Prediction
With simulation and fitting both in place, the natural next step is tooling that closes the loop between them — recovery checks or study-design guidance built on simulated surveys.
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 serofoi 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 serofoi 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 serofoi alternatives → · See all webmockr alternatives →
Recent activity from serofoi and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agoserofoiConstant FoI plots, r-hat plotting and shorter parameter names
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 1y agoserofoiSerological surveys can now be simulated end to end
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 2y agoserofoiSimulation functions added; fitted output simplified to a Stan fit
- 3y agoserofoiFirst release: three force-of-infection models and the core modules
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between serofoi and webmockr?
They serve adjacent needs but don't currently overlap on shipped themes. serofoi 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 serofoi better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. serofoi 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 serofoi?
Top serofoi alternatives in Analytics are ranked by recent ship velocity. Browse the "serofoi alternatives" section above for the current picks, or visit /alternatives/serofoi 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.