poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of accessibility and pegboard — release velocity, themes, recent moves, and the top alternatives to consider.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
accessibility, from IPEA's geo team, computes how reachable opportunities are given a travel matrix and land use data. Since the 1.0.0 rebuild it has widened well past reachability metrics: 1.1.0 added inequality and poverty estimation alongside spatial availability and balancing cost, 1.2.0 added the concentration index and Theil T, and 1.3.0 let spatial_availability() return results per origin-destination pair with the underlying balancing factors exposed.
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.
accessibility, from IPEA's geo team, computes how reachable opportunities are given a travel matrix and land use data. Since the 1.0.0 rebuild it has widened well past reachability metrics: 1.1.0 added inequality and poverty estimation alongside spatial availability and balancing cost, 1.2.0 added the concentration index and Theil T, and 1.3.0 let spatial_availability() return results per origin-destination pair with the underlying balancing factors exposed.
The package is moving from measuring access to measuring who is left out, and doing it by adding metrics rather than reworking the core. A second, quieter theme is generality — nearly every parameter that once took a single value now accepts vectors or lists, so users can sweep across cutoffs and decay specifications in one call. The decay family keeps growing, most recently with a logistic form.
Further inequality or decay functions are the most likely next addition, given that both families have grown steadily and neither shows signs of being considered complete; the entries give no indication of another breaking restructure.
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 accessibility or pegboard.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
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.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
See all accessibility 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. accessibility 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. accessibility 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 accessibility alternatives in Analytics are ranked by recent ship velocity. Browse the "accessibility alternatives" section above for the current picks, or visit /alternatives/accessibility 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.