← Back to home
Comparison · Analytics

crul vs spiro

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

Shared themes:ropensci

crul vs spiro: at a glance

Featurecrulspiro
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropensciexercise-physiology, data-import, sports-science, ropensci
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is spiro?

Cardiopulmonary exercise test data in R, one metabolic cart vendor at a time.

spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.

Read the full spiro trajectory →

crul vs spiro: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

S
spiro
ANALYTICS
0.0

Cardiopulmonary exercise test data in R, one metabolic cart vendor at a time.

◆ Current state

spiro imports and processes cardiopulmonary exercise testing data in R, handling the file formats that metabolic carts from Cosmed, Cortex, Vyntus, and ZAN emit, then interpolating, smoothing, and summarizing them into comparable variables. The bulk of ongoing work is vendor format compatibility rather than analysis features — 0.2.4 fixed Cosmed imports failing in rare cases and Cortex imports on newer devices, and 0.2.2 added English-language Vyntus files after 0.1.2 added French ones. The analysis side, spiro_max(), spiro_smooth() and spiro_plot(), has been stable for some time.

◆ Where it's heading

This is a mature rOpenSci package whose remaining work is dictated by other people's file formats. Each device firmware revision, each regional language variant, and each ggplot2 release generates maintenance, and that is what fills the changelog. The API itself settled early, with the 0.1.0 rOpenSci review pass renaming the protocol helpers to the pt_* prefix and 0.2.0 replacing the confusingly named spiro_import() with spiro_raw().

◆ Prediction

Expect the pattern to continue: import fixes as vendor formats shift and periodic plotting updates tracking ggplot2, with no indication of new analysis capability.

Alternatives to crul and spiro

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 crul or spiro.

See all crul alternatives → · See all spiro alternatives →

Recent activity from crul and spiro

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

  1. 1mo agospiroCosmed and Cortex import fixes for newer devices
  2. 1y agocrulMocking becomes a client parameter, independent of webmockr
  3. 1y agospiroEnglish-language Vyntus files supported
  4. 2y agocrulAsync requests become mockable through webmockr
  5. 2y agocrulDocumentation fixes and test helper tweak
  6. 3y agospiroR-devel compatibility and data frame printing fix
  7. 3y agocrulHTTP retries reach the async classes
  8. 3y agospirospiro_raw() replaces the misleading spiro_import()
  9. 3y agocrulClearer error for mismatched urls and disk lengths
  10. 3y agospiroFrench Vyntus support and protocol duration control
  11. 3y agospirospiro 0.1.1
  12. 4y agocrulAsyncQueue gains response accessors; results print as a summary

Frequently asked questions

What is the difference between crul and spiro?

Both compete on the same themes — ropensci — within Analytics. crul and spiro 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 crul better than spiro?

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

Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.

What are the best alternatives to spiro?

Top spiro alternatives in Analytics are ranked by recent ship velocity. Browse the "spiro alternatives" section above for the current picks, or visit /alternatives/spiro for the full list with editorial commentary on each.