poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of jmastats and rfacebookstat — 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.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
rfacebookstat wraps the Facebook Marketing API for R analysts, and nearly every release is a migration to a newer API version — v14, v15, v16, v19, v20 all appear in this window. Feature work rides along with those migrations: fbGetAdAccounts() gained a spend_cap field, and fbGetMarketingStat() gained use_unified_attribution_setting, which switches results to the ad-set-level attribution settings and overrides the older account-level argument.
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.
rfacebookstat wraps the Facebook Marketing API for R analysts, and nearly every release is a migration to a newer API version — v14, v15, v16, v19, v20 all appear in this window. Feature work rides along with those migrations: fbGetAdAccounts() gained a spend_cap field, and fbGetMarketingStat() gained use_unified_attribution_setting, which switches results to the ad-set-level attribution settings and overrides the older account-level argument.
The package's direction is set almost entirely by Meta's deprecation cycle, and the release notes read as a log of keeping up. The attribution work is the one strand with its own logic: an argument added in 2.10.0, then fixed in 2.12.1 when it turned out not to apply unless fetch_by was also used. Three versions cut within four and a half hours on one day in April 2023 show migrations being cleared in batches rather than steadily.
The next release will almost certainly be a migration to a newer Marketing API version, since that has triggered every version in this history; whether anything else ships with it depends on what Meta changes.
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 rfacebookstat.
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.
The utility layer under KWB's R packages, growing by accretion one helper at a time.
See all jmastats alternatives → · See all rfacebookstat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. jmastats and rfacebookstat 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 rfacebookstat 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 rfacebookstat alternatives in Analytics are ranked by recent ship velocity. Browse the "rfacebookstat alternatives" section above for the current picks, or visit /alternatives/rfacebookstat for the full list with editorial commentary on each.