poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of jmastats and pegboard — 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.
The Carpentries' lesson parser spends its releases keeping pace with tinkr underneath it.
pegboard reads and validates Carpentries lesson source, and its recent releases are dominated by tracking changes in tinkr, the Markdown layer it sits on. The 0.7.8 switch from yaml to frontmatter handling needed a hotfix three days later in 0.7.9; 0.7.6 was similarly a compatibility fix for a tinkr show argument change. The genuinely additive work — tabset panel support in 0.7.5, caution divs in 0.7.7 — is smaller and less frequent.
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.
pegboard reads and validates Carpentries lesson source, and its recent releases are dominated by tracking changes in tinkr, the Markdown layer it sits on. The 0.7.8 switch from yaml to frontmatter handling needed a hotfix three days later in 0.7.9; 0.7.6 was similarly a compatibility fix for a tinkr show argument change. The genuinely additive work — tabset panel support in 0.7.5, caution divs in 0.7.7 — is smaller and less frequent.
This is infrastructure whose roadmap is largely set by its dependency. Contributor churn is visible in the release notes, with several first-time contributors and the release role passing between maintainers, which suggests a community project maintained in bursts rather than to a plan. New lesson-authoring features arrive when someone contributes one, not on a cadence.
The next release will most likely be another tinkr compatibility pass or a small addition to the set of recognised div types, following the pattern of every release in this window.
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 pegboard.
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 pegboard alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. jmastats and pegboard 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 pegboard 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 pegboard alternatives in Analytics are ranked by recent ship velocity. Browse the "pegboard alternatives" section above for the current picks, or visit /alternatives/pegboard for the full list with editorial commentary on each.