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 StreamCatTools — 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.
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
StreamCatTools is the R client for the US EPA's StreamCat and LakeCat watershed metrics datasets. Through 2025 it worked almost entirely against the StreamCat web API, and much of its release history is about making those HTTP calls survive real conditions — POST bodies for long COMID lists, tryCatch around service outages, tests that skip when the service is down. 0.11.0 in May 2026 introduces a different data path.
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.
StreamCatTools is the R client for the US EPA's StreamCat and LakeCat watershed metrics datasets. Through 2025 it worked almost entirely against the StreamCat web API, and much of its release history is about making those HTTP calls survive real conditions — POST bodies for long COMID lists, tryCatch around service outages, tests that skip when the service is down. 0.11.0 in May 2026 introduces a different data path.
The newest release adds lc_get_watershed(), which returns a lake watershed as an sf feature by reading an S3-hosted, HUC2-partitioned GeoParquet dataset with DuckDB, optional HUC2 filtering, retries and multi-threading. That is a materially different access model from the web service the rest of the package uses. Alongside it, 0.10.0 added National Nutrient Inventory access and nitrogen/phosphorus budget plotting, extending the package past retrieval into presentation.
If the GeoParquet path proves faster and more reliable than the web service, migrating more retrieval functions onto it is the obvious next move. The entries do not say whether EPA intends to publish the full metric catalogue in that format.
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 StreamCatTools.
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
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 StreamCatTools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. igoR and StreamCatTools 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 StreamCatTools 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 StreamCatTools alternatives in Analytics are ranked by recent ship velocity. Browse the "StreamCatTools alternatives" section above for the current picks, or visit /alternatives/streamcattools for the full list with editorial commentary on each.