← Back to home
Comparison · Analytics

simulist vs webmockr

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

simulist vs webmockr: at a glance

Featuresimulistwebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepiverse-trace, outbreak-simulation, line-list, data-realismhttp-mocking, testing, httr2, ropensci
Last editorial update7h ago1h ago
WebsiteVisit →Visit →

What is simulist?

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

Read the full simulist trajectory →

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.

Read the full webmockr trajectory →

simulist vs webmockr: editorial side-by-side

S
simulist
ANALYTICS
0.0

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

◆ Current state

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

◆ Where it's heading

The scope moved outward in two steps. 0.5.0 added truncate_linelist() and messy_linelist() to produce right-truncated snapshots and data with missingness and inconsistencies; 0.6.0 added censor_linelist() for grouping dates into intervals with a weekend-reporting effect. The simulation core has meanwhile settled — 0.7.0's changes are interface polish: weighted sex sampling and <epiparameter> objects accepted for reporting_delay.

◆ Prediction

Post-processing is where the recent work is, so further realism controls — additional reporting artefacts or interval schemes — are a likelier next step than new epidemic model structures.

W
webmockr
ANALYTICS
0.0

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 simulist 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 simulist or webmockr.

See all simulist alternatives → · See all webmockr alternatives →

Recent activity from simulist and webmockr

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

  1. 6mo agosimulistJOSS paper corrections
  2. 6mo agosimulistWeighted sex sampling and epiparameter objects for reporting delays
  3. 11mo agosimulistcensor_linelist() adds interval censoring and a weekend effect
  4. 1y agowebmockrvcr dependency severed
  5. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  6. 1y agosimulistPost-processing arrives: truncated snapshots and deliberately messy line lists
  7. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  8. 1y agosimulistEvery sim_*() argument gains a default
  9. 2y agowebmockrhttr2 joins httr and crul as a supported client
  10. 2y agosimulistInfectious period replaces contact interval; time-varying fatality risk added
  11. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  12. 3y agowebmockrRegex URI matching fixed

Frequently asked questions

What is the difference between simulist and webmockr?

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

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

Top simulist alternatives in Analytics are ranked by recent ship velocity. Browse the "simulist alternatives" section above for the current picks, or visit /alternatives/simulist 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.