tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of igoR and timbr — release velocity, themes, recent moves, and the top alternatives to consider.
igoR reached 1.0.0 with no user-visible change, then spent three releases on AI-assisted cleanup
igoR provides access to Intergovernmental Organizations (IGO) databases from the Correlates of War project. The dataset and public API have been stable for years; recent releases are almost entirely maintenance. 1.0.0 in January 2026 raised the minimum R version to 3.6.0 and stated explicitly that users would see no change.
Three years dormant, timbr returns with dplyr verbs that finally respect tree structure
timbr provides a 'forest' class for nested tree data in R, letting users navigate parent/child relationships with tidyverse-style verbs. After its last release in May 2023, the package sat untouched for over three years before 0.3.0 landed in July 2026. That release is dominated by correctness work on the structural invariants that everything else depends on.
igoR provides access to Intergovernmental Organizations (IGO) databases from the Correlates of War project. The dataset and public API have been stable for years; recent releases are almost entirely maintenance. 1.0.0 in January 2026 raised the minimum R version to 3.6.0 and stated explicitly that users would see no change.
Development has shifted to documentation and internal consistency, and the mechanism is notable: 1.0.2 and 1.0.3 both describe AI-assisted editing and refactoring, part of a sweep the same maintainer ran across several packages in mid-2026. The one substantive fix in the window is igo_dyadic() computing dyadid from both state codes as documented. Everything else is dependency bumps and message wording.
With the internals refactored and documentation reviewed, further releases are likely to track upstream Correlates of War data updates rather than change the API. The entries give no indication of a pending data revision.
timbr provides a 'forest' class for nested tree data in R, letting users navigate parent/child relationships with tidyverse-style verbs. After its last release in May 2023, the package sat untouched for over three years before 0.3.0 landed in July 2026. That release is dominated by correctness work on the structural invariants that everything else depends on.
The arc is from a working prototype toward a class that behaves correctly under the full dplyr surface. 0.3.0 implements relocate(), rows_patch() and rows_update() for forests and makes select() always preserve the internal node column, closing the gaps where a standard verb would silently break the tree. The deprecation of map_forest() in favour of traverse(), begun in 0.2.2, is now complete.
With the verb coverage gaps closed and the long deprecation cycle finished, the next release is likely to extend dplyr method coverage further rather than change the forest model. The entries do not indicate what prompted the three-year gap, so the sustainability of this cadence is unclear.
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 igoR or timbr.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. igoR and timbr 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. igoR and timbr 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 igoR alternatives in Analytics are ranked by recent ship velocity. Browse the "igoR alternatives" section above for the current picks, or visit /alternatives/igor for the full list with editorial commentary on each.
Top timbr alternatives in Analytics are ranked by recent ship velocity. Browse the "timbr alternatives" section above for the current picks, or visit /alternatives/timbr for the full list with editorial commentary on each.