poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of jmastats and tern.rbmi — release velocity, themes, recent moves, and the top alternatives to consider.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
The package treats bundled data as the thing that must not go stale, and the retrieval API as broadly finished. Where code does change, it is about being a well-behaved client — request intervals to reduce server load, messages when returned data contains missing values, corrected station coordinates. Capability growth happens in single steps, roughly once a year.
The next release is most likely another dated dataset refresh; a further extension of jma_collect() to a new observation type is plausible but the entries show no specific one being prepared.
tern.rbmi renders the output of {rbmi} reference-based multiple imputation analyses into tern tables for clinical reporting. Its three most recent releases exist to satisfy CRAN: restricting vignette builds to gcc, adding V8 to Suggests, and a plain resubmission. No user-facing functionality has changed in the visible window, and the three older entries now backfilled are version-bump automation.
This is a thin adapter package and behaves like one — it moves when CRAN or an upstream dependency forces it to. Between 2022 and 2024 the feed shows only version bumps, and the 2025 releases are packaging concerns rather than analysis changes. The newly surfaced 2022 entries reinforce rather than change that reading.
Expect the next release to be triggered by a CRAN check failure or an {rbmi} update rather than by new tabulation features.
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 jmastats or tern.rbmi.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
The Carpentries' lesson skin, rebuilt on Bootstrap 5 with dark mode and a wider reach.
A project-bound modelling package that shipped its final scenario workflow and stopped.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
See all jmastats alternatives → · See all tern.rbmi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. jmastats and tern.rbmi 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. jmastats and tern.rbmi 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 jmastats alternatives in Analytics are ranked by recent ship velocity. Browse the "jmastats alternatives" section above for the current picks, or visit /alternatives/jmastats for the full list with editorial commentary on each.
Top tern.rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "tern.rbmi alternatives" section above for the current picks, or visit /alternatives/tern-rbmi for the full list with editorial commentary on each.