poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of netrankr and rgoogleads — release velocity, themes, recent moves, and the top alternatives to consider.
A centrality package that absorbed an abandoned neighbour rather than let its functions vanish.
netrankr computes centrality rankings on networks using partial orders rather than committing to a single index, and lets users build their own indices from relational components. The latest release folds in functions from the archived NetSwan package and clears deprecated igraph calls. Earlier work removed the midpoint calculation from rank_intervals, a change the notes themselves flag as possibly breaking.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
netrankr computes centrality rankings on networks using partial orders rather than committing to a single index, and lets users build their own indices from relational components. The latest release folds in functions from the archived NetSwan package and clears deprecated igraph calls. Earlier work removed the midpoint calculation from rank_intervals, a change the notes themselves flag as possibly breaking.
Development is sparse and driven by ecosystem pressure — igraph deprecations, CRAN archival of related packages, JOSS submission requirements. The analytic core has been stable since the partial-order framework was established; what changes is the surrounding surface and its compatibility with a moving graph stack. Absorbing NetSwan is the first real expansion in years.
Expect further igraph compatibility passes; whether the NetSwan absorption is a one-off rescue or the start of consolidating orphaned network packages is not something these entries settle.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
Development is reactive by design — the package changes when Google changes, and the notes rarely describe anything else. The deeper rework happened earlier, in 0.7.0, when request generation was centralised into gads_make_request() and gads_customer() was rewritten onto SearchStream after the old get method was retired. Since then the structure has held and releases have thinned to version bumps, with the most recent gap running over a year.
The next release will be a migration to a newer Google Ads API version, and on this history it will arrive when the current one nears sunset rather than on any schedule of the maintainer's own.
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 netrankr or rgoogleads.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
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.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
See all netrankr alternatives → · See all rgoogleads alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. netrankr and rgoogleads 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. netrankr and rgoogleads 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 netrankr alternatives in Analytics are ranked by recent ship velocity. Browse the "netrankr alternatives" section above for the current picks, or visit /alternatives/netrankr-r for the full list with editorial commentary on each.
Top rgoogleads alternatives in Analytics are ranked by recent ship velocity. Browse the "rgoogleads alternatives" section above for the current picks, or visit /alternatives/rgoogleads for the full list with editorial commentary on each.