← Back to home
Comparison · Analytics

DataSpaceR vs webmockr

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

DataSpaceR vs webmockr: at a glance

FeatureDataSpaceRwebmockr
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themeshiv-research, immunology-data, api-client, antibody-sequenceshttp-mocking, testing, httr2, ropensci
Last editorial update6h ago1h ago
WebsiteVisit →Visit →

What is DataSpaceR?

DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.

The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.

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

DataSpaceR vs webmockr: editorial side-by-side

D
DataSpaceR
ANALYTICS
2.5

DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.

◆ Current state

The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.

◆ Where it's heading

The package is converging on one query idiom — build a filtered object, then fetch — instead of per-domain grid methods, and each class now accepts multiple studies or antibodies rather than one. The 1.0.1 patch suggests the rewrite dropped functionality that users noticed, and it was put back rather than redesigned.

◆ Prediction

With DAASH access in place and the query surface unified, the next work is most likely more sequence-domain coverage and follow-up fixes to the batched query paths introduced in 1.0.1.

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

See all DataSpaceR alternatives → · See all webmockr alternatives →

Recent activity from DataSpaceR and webmockr

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

  1. 9d agoDataSpaceRLANL metadata requests restored and BCR queries batched
  2. 1mo agoDataSpaceRQuery API rebuilt and DAASH antibody sequence access added
  3. 1y agowebmockrvcr dependency severed
  4. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  5. 1y agoDataSpaceRFixes for antibody and donor queries
  6. 1y agoDataSpaceRLANL metadata added to neutralising-antibody pulls
  7. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  8. 2y agowebmockrhttr2 joins httr and crul as a supported client
  9. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  10. 3y agowebmockrRegex URI matching fixed
  11. 4y agoDataSpaceRSession fix for CDS reports and snake-case bindings

Frequently asked questions

What is the difference between DataSpaceR and webmockr?

They serve adjacent needs but don't currently overlap on shipped themes. DataSpaceR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is DataSpaceR better than webmockr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DataSpaceR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to DataSpaceR?

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