tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of riem and typst-gather — release velocity, themes, recent moves, and the top alternatives to consider.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.
With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
The 0.2.0 restructuring is the tell: subcommands with backwards compatibility, config readable from stdin, and every diagnostic message moved to stderr so stdout carries nothing but JSON. Those are the conventions of a tool meant to be called by another program, not typed by a person. Given its origin inside Quarto's toolchain, the plausible consumer is a build system that needs to know a document's package requirements before deciding what to fetch.
The analyze path currently reports imports; the natural extension visible from here is acting on that report — lockfile output or verification that a cache satisfies a document's dependency set — though the entries do not commit to either.
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 riem or typst-gather.
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.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all riem alternatives → · See all typst-gather alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. riem and typst-gather 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. riem and typst-gather 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 riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem for the full list with editorial commentary on each.
Top typst-gather alternatives in Analytics are ranked by recent ship velocity. Browse the "typst-gather alternatives" section above for the current picks, or visit /alternatives/typst-gather for the full list with editorial commentary on each.