r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
crul vs forestly
A side-by-side editorial comparison of crul and forestly — release velocity, themes, recent moves, and the top alternatives to consider.
crul vs forestly: at a glance
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.
What is forestly?
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
crul vs forestly: editorial side-by-side
crul
0.0ANALYTICS
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.
forestly
0.0ANALYTICS
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
◆ Current state
forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.
◆ Where it's heading
The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.
◆ Prediction
Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.
Alternatives to crul and forestly
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 forestly.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
cloudml
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all crul alternatives → · See all forestly alternatives →
Recent activity from crul and forestly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agoforestlyDownload button, AE filter label and diff toggle become optional
- 11mo agoforestlyStatic RTF forest plots join the interactive output ⚡
- 1y agocrulMocking becomes a client parameter, independent of webmockr ⚡
- 1y agoforestlyreactR 0.6.0 rendering fix and slider label control
- 2y agocrulAsync requests become mockable through webmockr
- 2y agoforestlyTreatment group selection and rough-edge fixes
- 2y agocrulDocumentation fixes and test helper tweak
- 3y agoforestlyFirst release on GitHub and CRAN
- 3y agocrulHTTP retries reach the async classes
- 3y agocrulClearer error for mismatched urls and disk lengths
- 4y agocrulAsyncQueue gains response accessors; results print as a summary
Frequently asked questions
What is the difference between crul and forestly?
They serve adjacent needs but don't currently overlap on shipped themes. crul and forestly 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 forestly?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul and forestly 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 forestly?
Top forestly alternatives in Analytics are ranked by recent ship velocity. Browse the "forestly alternatives" section above for the current picks, or visit /alternatives/forestly for the full list with editorial commentary on each.