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 spsurvey — 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.
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
spsurvey implements design and analysis for spatially balanced environmental survey samples, the GRTS methodology used in large-scale monitoring programs. The 5.0.0 rewrite is the defining event in its history, and everything in this window is aftercare. 5.6.0 in September 2025 finally removed the startup message warning users about that upgrade, several years 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.
spsurvey implements design and analysis for spatially balanced environmental survey samples, the GRTS methodology used in large-scale monitoring programs. The 5.0.0 rewrite is the defining event in its history, and everything in this window is aftercare. 5.6.0 in September 2025 finally removed the startup message warning users about that upgrade, several years on.
The direction is toward standard R idioms and away from bespoke ones. 5.4.0 introduced sp_frame and sp_design classes so plot() and summary() work directly, keeping sp_plot() and sp_summary() only for backwards compatibility; 5.5.0 moved warnings from cat() to message() so they can be suppressed normally, and added adjwgtNR() for non-response weight adjustment. Documentation is being pushed off CRAN onto the package website, with only the Start Here vignette remaining. Release cadence is slow — five releases across roughly four years.
With the migration messaging retired and the class system settled, further releases are likely to stay in maintenance and statistical-detail territory. Nothing in the entries suggests another rewrite.
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 spsurvey.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
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
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all igoR alternatives → · See all spsurvey alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. igoR and spsurvey 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 spsurvey 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 spsurvey alternatives in Analytics are ranked by recent ship velocity. Browse the "spsurvey alternatives" section above for the current picks, or visit /alternatives/spsurvey for the full list with editorial commentary on each.