sasr
An R package that runs SAS code in a SAS session and hands the results back.
A side-by-side editorial comparison of adaR and ipumsr — release velocity, themes, recent moves, and the top alternatives to consider.
An R binding to the ada URL parser, now maintained by a research-software group.
adaR wraps the ada-url C++ library to give R a WHATWG-compliant URL parser with vectorised accessors, setters and clearers for every URL component. The latest release is a performance improvement to ada_url_parse. Maintenance moved from an individual to the gesistsa organisation, which also bumped the vendored parser.
ipumsr is collapsing a dozen collection-specific APIs into one extract vocabulary.
ipumsr is the R client for the IPUMS API, covering microdata, aggregate-data and now DHS collections. The dominant work of the last two years has been replacing per-collection functions with generic ones: define_extract_micro() for all microdata, then define_extract_agg() and read_ipums_agg() for the aggregate projects. Each new collection now arrives as an argument value rather than a new function.
adaR wraps the ada-url C++ library to give R a WHATWG-compliant URL parser with vectorised accessors, setters and clearers for every URL component. The latest release is a performance improvement to ada_url_parse. Maintenance moved from an individual to the gesistsa organisation, which also bumped the vendored parser.
The package reached feature completeness quickly — the accessor, setter and clearer families were all exported within months — and has since settled into tracking upstream ada-url and tuning parse speed. Note that this feed is backfilled out of order: the 0.1.0 initial release carries a later publication date than 0.3.0 and 0.3.1, so feed position does not reflect release sequence.
Expect continued ada-url version bumps and performance work; the API surface appears settled.
ipumsr is the R client for the IPUMS API, covering microdata, aggregate-data and now DHS collections. The dominant work of the last two years has been replacing per-collection functions with generic ones: define_extract_micro() for all microdata, then define_extract_agg() and read_ipums_agg() for the aggregate projects. Each new collection now arrives as an argument value rather than a new function.
The package is converging on a single extract-definition surface, and it is retiring the old path rather than keeping both. Collection-specific functions have moved through deprecation to defunct within about two release cycles, and legacy spatial and codebook readers have been dropped outright along with their raster and sp dependencies. The cost is paid by users: each generalization has broken working code.
The remaining collection-specific entry points, chiefly the NHGIS-named ones, are the obvious next candidates for deprecation, and further IPUMS projects will most likely be added as collection arguments rather than new functions.
Other DevOps 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 adaR or ipumsr.
An R package that runs SAS code in a SAS session and hands the results back.
ralger stopped scraping only web pages and started scraping the files on them.
ieugwasr's release notes are a record of OpenGWAS tightening the tap.
bskyr grew from a Bluesky scraper into a full read-write client, DMs included.
Sanity is widening the surface agents can act on while forcing its own packages onto modern Node.
Dapr is shipping fixes across three release branches at once, most of them in workflows.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. adaR and ipumsr 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. adaR and ipumsr 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 DevOps products to evaluate alongside.
Top adaR alternatives in DevOps are ranked by recent ship velocity. Browse the "adaR alternatives" section above for the current picks, or visit /alternatives/adar-r for the full list with editorial commentary on each.
Top ipumsr alternatives in DevOps are ranked by recent ship velocity. Browse the "ipumsr alternatives" section above for the current picks, or visit /alternatives/ipumsr-r for the full list with editorial commentary on each.