chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
A side-by-side editorial comparison of forestly and markdown — 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.
A package that finished, declared itself done, and handed its core function to a successor.
The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.
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.
The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.
This is a controlled retirement rather than abandonment. The maintainer closed out the outstanding feature work first, announced the succession explicitly, and only then reduced the package to a compatibility surface. What remains is a stable shim for the installed base while new work happens in a package with a different name and scope.
Expect only CRAN-driven fixes here from now on, with any genuinely new rendering capability appearing in litedown instead. The entries state this policy directly, so the main open question is how long the wrapper is kept before deprecation warnings appear.
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 markdown.
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
Six years since the last functional change, and Google renamed the service it wraps in the release before that
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
See all forestly alternatives → · See all markdown alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. forestly and markdown 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 markdown 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 markdown alternatives in Analytics are ranked by recent ship velocity. Browse the "markdown alternatives" section above for the current picks, or visit /alternatives/markdown for the full list with editorial commentary on each.