tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of mantis and tinkr — release velocity, themes, recent moves, and the top alternatives to consider.
Thirteen months of rOpenSci review turned a pre-release into a 1.0 with a stable API
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
tinkr parses Markdown into XML, lets callers manipulate it with XPath, and writes it back out — the yarn R6 class is the whole interface. Its development is defined by a single hard problem: surviving the round trip without corrupting syntax the XML representation does not natively model. Maintenance is shared between two active contributors and release cadence is roughly annual.
mantis builds interactive time-series reports — heatmaps, multipanel plots, alert tables — over routinely collected data, and its release history is essentially an rOpenSci peer-review log. The package went from a January 2025 pre-release that warned of breaking changes ahead, through submission and CRAN acceptance, to a 1.0.0 in October 2025 that locked the API. Since then it has shipped only two small fixes, the most recent chasing a dplyr 1.2.0 deprecation.
The breaking changes cluster entirely below 1.0.0 and stop there: `period` became `timepoint_unit`, `save_directory`/`save_filename` became `file`, `function_call` became `expression`. Post-1.0 the work is defensive — stricter POSIXt validation, timepoint limits that clamp to the data rather than inventing plot points, daylight-savings handling. The feed reads as a package that has finished defining itself and is now maintaining compatibility with the tidyverse underneath it.
With the API frozen and review complete, expect the next release to be another upstream-compatibility fix rather than new report types. There is no signal in these entries about planned feature work.
tinkr parses Markdown into XML, lets callers manipulate it with XPath, and writes it back out — the yarn R6 class is the whole interface. Its development is defined by a single hard problem: surviving the round trip without corrupting syntax the XML representation does not natively model. Maintenance is shared between two active contributors and release cadence is roughly annual.
Each release extends the set of constructs that get protected across the round trip — curly braces, escaped brackets, inline math, dollar signs used as currency, French-style dollars, fenced divs, frontmatter. The 0.3.0 notes also add get_protected(), append_md(), and prepend_md(), which is the first sign of building a manipulation API on top of the protection machinery rather than only widening it.
Expect the protection list to keep growing toward full Quarto syntax coverage, which the first release named as the long-term goal and which fenced divs and frontmatter both move toward.
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 mantis or tinkr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all mantis alternatives → · See all tinkr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ropensci — within Analytics. mantis and tinkr 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. mantis and tinkr 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 mantis alternatives in Analytics are ranked by recent ship velocity. Browse the "mantis alternatives" section above for the current picks, or visit /alternatives/mantis for the full list with editorial commentary on each.
Top tinkr alternatives in Analytics are ranked by recent ship velocity. Browse the "tinkr alternatives" section above for the current picks, or visit /alternatives/tinkr for the full list with editorial commentary on each.