← Back to home
Comparison · Analytics

igoR vs timbr

A side-by-side editorial comparison of igoR and timbr — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r

igoR vs timbr: at a glance

FeatureigoRtimbr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, political science, data access, documentationr, data structures, dplyr, tree data
Last editorial update33m ago33m ago
WebsiteVisit →Visit →

What is igoR?

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.

Read the full igoR trajectory →

What is timbr?

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.

Read the full timbr trajectory →

igoR vs timbr: editorial side-by-side

I
igoR
ANALYTICS
0.0

igoR reached 1.0.0 with no user-visible change, then spent three releases on AI-assisted cleanup

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

T
timbr
ANALYTICS
0.0

Three years dormant, timbr returns with dplyr verbs that finally respect tree structure

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to igoR and timbr

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.

See all igoR alternatives → · See all timbr alternatives →

Recent activity from igoR and timbr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agotimbrForests gain relocate/rows_patch/rows_update; map_forest now defunct
  2. 1mo agoigoRigo_dyadic() fixes dyadid computation; internals refactored
  3. 2mo agoigoRDocumentation reviewed with AI-assisted editing
  4. 5mo agoigoRCOPYRIGHTS updated; vignettes migrated to Quarto
  5. 7mo agoigoRFirst major version; minimum R raised to 3.6.0
  6. 1y agoigoRRoutine documentation update
  7. 2y agoigoRRecode helpers for IGO year, state year and dyadic data
  8. 3y agotimbrmap_forest() renamed to traverse() and deprecated
  9. 3y agotimbrArgument rename in rowwise.forest() and CRAN check fixes
  10. 3y agotimbrForest headers now print the tree structure

Frequently asked questions

What is the difference between igoR and timbr?

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.

Is igoR better than timbr?

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.

What are the best alternatives to igoR?

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.

What are the best alternatives to timbr?

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.