r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
forestly vs giscoR
A side-by-side editorial comparison of forestly and giscoR — release velocity, themes, recent moves, and the top alternatives to consider.
forestly vs giscoR: at a glance
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.
What is giscoR?
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
forestly vs giscoR: editorial side-by-side
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.
giscoR
0.0ANALYTICS
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
◆ Current state
giscoR downloads Eurostat GISCO administrative and statistical geodata — countries, NUTS regions, LAUs, urban audit units — as sf objects. The 1.0.0 release in December 2025 rebuilt the package on httr2, preferred GeoPackage downloads, reorganised the cache into topic folders, and moved the dataset database itself into the cache so it can be refreshed independently. Releases since have been a cache-persistence fix, a configurable timeout and an internals refactor.
◆ Where it's heading
The package is decoupling itself from Eurostat's publication calendar. Historically each new GISCO vintage required a release that bumped default years and rebuilt an internal dataset; after 1.0.0 a user can call gisco_get_cached_db(update_cache = TRUE) and reach new data without waiting. The follow-up releases are consistent with a project in consolidation — fixing the cache it just introduced, exposing a timeout for slow downloads, and tidying internals.
◆ Prediction
With the database now self-updating, expect releases to shift toward download reliability and new GISCO endpoints rather than annual dataset bumps; the timeout option in 1.1.0 suggests large downloads are the current pain point.
Alternatives to forestly and giscoR
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 forestly or giscoR.
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
crul
crul took mocking back from webmockr and made it a property of the client itself
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
See all forestly alternatives → · See all giscoR alternatives →
Recent activity from forestly and giscoR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agogiscoRInternal refactor with faster mocked tests
- 4mo agogiscoRDownload timeout becomes configurable
- 5mo agoforestlyDownload button, AE filter label and diff toggle become optional
- 6mo agogiscoRCache persistence fixed; urban audit defaults to 2024
- 7mo agogiscoR1.0 caches the dataset index so new vintages need no release ⚡
- 11mo agoforestlyStatic RTF forest plots join the interactive output ⚡
- 1y agogiscoRSource filtering fixed in gisco_get_lau()
- 1y agoforestlyreactR 0.6.0 rendering fix and slider label control
- 1y agogiscoR2024 datasets and year arguments for education and healthcare
- 2y agoforestlyTreatment group selection and rough-edge fixes
- 3y agoforestlyFirst release on GitHub and CRAN
Frequently asked questions
What is the difference between forestly and giscoR?
They serve adjacent needs but don't currently overlap on shipped themes. forestly and giscoR 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 forestly better than giscoR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forestly and giscoR 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 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.
What are the best alternatives to giscoR?
Top giscoR alternatives in Analytics are ranked by recent ship velocity. Browse the "giscoR alternatives" section above for the current picks, or visit /alternatives/giscor for the full list with editorial commentary on each.