← Back to home
Comparison · Analytics

excluder vs webmockr

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

excluder vs webmockr: at a glance

Featureexcluderwebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-data, data-cleaning, r-package, qualtricshttp-mocking, testing, httr2, ropensci
Last editorial update48m ago1h ago
WebsiteVisit →Visit →

What is excluder?

A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.

excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.

Read the full excluder 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 →

excluder vs webmockr: editorial side-by-side

E
excluder
ANALYTICS
0.0

A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.

◆ Current state

excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.

◆ Where it's heading

The package is stable and its maintenance load comes from things it does not control: the {iptools} package leaving CRAN, {tidyselect} deprecating the .data pronoun, IP-geolocation tests breaking when the underlying address data shifts. Much of that work is about staying installable, not about better exclusions. Note that several of these entries were backfilled into the feed within the same two-minute window and are not in version order.

◆ Prediction

The next release will most likely be another dependency or CRAN-check response rather than a new exclusion criterion, following the pattern of the last three.

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

See all excluder alternatives → · See all webmockr alternatives →

Recent activity from excluder and webmockr

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

  1. 1y agowebmockrvcr dependency severed
  2. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  3. 1y agoexcluderInternet-dependent tests and examples made conditional
  4. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  5. 2y agowebmockrhttr2 joins httr and crul as a supported client
  6. 2y agoexcluderqualtrics_fetch2 dataset and tidyselect deprecation fixes
  7. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  8. 3y agoexcluderCRAN acceptance and graceful IP-lookup failure
  9. 3y agoexcluderdplyr 1.0.8 across()/is.na() compatibility fix
  10. 3y agoexcluderuse_labels(), rename_columns(), and orientation-agnostic resolution
  11. 3y agoexcluderSwaps iptools for ipaddress
  12. 3y agowebmockrRegex URI matching fixed

Frequently asked questions

What is the difference between excluder and webmockr?

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

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

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