r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of forestly and graphicalMCP — release velocity, themes, recent moves, and the top alternatives to consider.
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.
graphicalMCP is a narrow statistical tool being hardened rather than grown.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
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.
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.
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.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
The changelog reads as a package settling into reference-implementation status: procedure coverage widened once, then the work turned to proving the two computational routes through the same graph agree with each other. That agreement is the whole promise of this kind of tool, since the closure-based calculation is the definition and the rejection-based one is the fast path everyone actually runs. The openpharma move points the same direction — shared maintenance rather than a single author's project.
The entries show no feature roadmap, only correctness and validation work, so the next release is most likely another consistency or precision fix rather than a new procedure.
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 graphicalMCP.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all forestly alternatives → · See all graphicalMCP alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-language — within Analytics. forestly and graphicalMCP 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forestly and graphicalMCP 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.
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.
Top graphicalMCP alternatives in Analytics are ranked by recent ship velocity. Browse the "graphicalMCP alternatives" section above for the current picks, or visit /alternatives/graphicalmcp for the full list with editorial commentary on each.