← Back to home
Comparison · Analytics

tabnet vs webmockr

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

tabnet vs webmockr: at a glance

Featuretabnetwebmockr
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themestabular-deep-learning, torch, tidymodels, parsniphttp-mocking, testing, httr2, ropensci
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is tabnet?

A tabular deep-learning model in R that keeps widening what counts as a tabular task.

tabnet ports the TabNet attentive tabular architecture to R on torch, wired into tidymodels through parsnip so it slots into workflows, tuning, and case weights like any other engine. The model surface has grown well past plain supervised fitting: unsupervised pretraining, missing values in predictors, multi-outcome fitting, hierarchical multi-label classification, and built-in explainability via tabnet_explain(). The 0.9.x line has been consolidating rather than adding, with 0.9.0 finally making hierarchical classification work correctly by accounting for the ancestor matrix.

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

tabnet vs webmockr: editorial side-by-side

T
tabnet
ANALYTICS
2.5

A tabular deep-learning model in R that keeps widening what counts as a tabular task.

◆ Current state

tabnet ports the TabNet attentive tabular architecture to R on torch, wired into tidymodels through parsnip so it slots into workflows, tuning, and case weights like any other engine. The model surface has grown well past plain supervised fitting: unsupervised pretraining, missing values in predictors, multi-outcome fitting, hierarchical multi-label classification, and built-in explainability via tabnet_explain(). The 0.9.x line has been consolidating rather than adding, with 0.9.0 finally making hierarchical classification work correctly by accounting for the ancestor matrix.

◆ Where it's heading

Two threads run through the release history. The first is task surface — each minor version tends to admit a class of problem the model previously could not express, from missing data to hierarchy to imbalanced binary outcomes. The second is torch-level performance and correctness, visible in the torch_ignite_adam default that cut pretraining time roughly 30% and the fix for optimizers frozen after checkpointing on cuda and mps. Tidymodels integration is treated as a first-class obligation, with parsnip breaking changes tracked release by release.

◆ Prediction

The hierarchical path is the least finished: 0.5.0 introduced it and 0.9.0 only just made it effective, so the next releases most likely extend evaluation and explainability to hierarchical fits rather than adding another task type.

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

See all tabnet alternatives → · See all webmockr alternatives →

Recent activity from tabnet and webmockr

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

  1. 21d agotabnetvip dependency moves to r-universe
  2. 2mo agotabnetHierarchical classification made effective, augment() added
  3. 6mo agotabnetentmax15 and sparsemax15 masks, AUM loss for imbalanced data
  4. 1y agowebmockrvcr dependency severed
  5. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  6. 1y agotabnetBugfix release for R 4.5 and dials tuning
  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. 2y agotabnetCase weights and warm-start parameters via parsnip
  10. 2y agotabnetHierarchical multi-label classification via data.tree
  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 tabnet and webmockr?

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

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

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