Sanity
Sanity is widening the surface agents can act on while forcing its own packages onto modern Node.
A side-by-side editorial comparison of ipumsr and secretbase — release velocity, themes, recent moves, and the top alternatives to consider.
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.
secretbase quietly grew from a hashing package into a serialization toolkit
secretbase provides SHA-3, SHAKE, BLAKE3 and related hashing in R with a small C footprint and no dependencies. Over 2026 it has accumulated a second identity: CBOR, base58, JSON and URL-safe base64 encoders and decoders now sit alongside the hash functions. Releases are frequent, short and each does one thing — a format added, a conversion sped up, an undefined-behaviour warning cleared.
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.
secretbase provides SHA-3, SHAKE, BLAKE3 and related hashing in R with a small C footprint and no dependencies. Over 2026 it has accumulated a second identity: CBOR, base58, JSON and URL-safe base64 encoders and decoders now sit alongside the hash functions. Releases are frequent, short and each does one thing — a format added, a conversion sped up, an undefined-behaviour warning cleared.
The additions are not arbitrary. CBOR is a binary format for structured data, JSON its text counterpart, base58 the checksummed encoding used for identifiers — together they cover what a process needs to put an R object on a wire and get it back, which is a different job from digesting bytes. The maintainer also maintains R's high-performance messaging stack, and a dependency-free codec that handles integers, floats, strings, raw vectors and lists is exactly what that stack would consume.
Every format added so far has come with an RFC number and a minimal implementation rather than a wrapped library, so further additions are likely to follow the same pattern; the encoders are also being optimized after they land, suggesting performance passes on CBOR and JSON before anything new.
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 ipumsr or secretbase.
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.
rtoot reached 1.0 by rebuilding on httr2 rather than by adding anything new.
A stable R data-structure package whose releases are now mostly compiler and checker upkeep.
Z-Wave JS UI is hardening its network surface while handing issue triage to agents.
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
See all ipumsr alternatives → · See all secretbase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within DevOps. ipumsr and secretbase 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. ipumsr and secretbase 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 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.
Top secretbase alternatives in DevOps are ranked by recent ship velocity. Browse the "secretbase alternatives" section above for the current picks, or visit /alternatives/secretbase-r for the full list with editorial commentary on each.