magrittr
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
A side-by-side editorial comparison of Fiber and zip — release velocity, themes, recent moves, and the top alternatives to consider.
Fiber v3 has sat in release candidate for months while v2 gets one-line patches
The feed carries two lines that barely touch. Fiber v2 receives narrow maintenance releases — a lock cleanup, an X-Real-IP backport, an HTML escaping fix, a CVE patch — most containing a single merged PR. The v3 line, last visible here at rc.3, is where the actual work is: native net/http and fasthttp handler support, Express-style request and response handlers, HostClient and LBClient in the client package.
zip 3.0 added encryption, turning a plumbing package into a complete archive tool.
zip creates and extracts archives from R without depending on external tools. Its 2.x line was incremental — a type column in zip_list(), symlink handling on Unix, hidden shared-library symbols. Version 3.0.0 changed the package's shape by adding password-protected archives and vectorized extraction.
The feed carries two lines that barely touch. Fiber v2 receives narrow maintenance releases — a lock cleanup, an X-Real-IP backport, an HTML escaping fix, a CVE patch — most containing a single merged PR. The v3 line, last visible here at rc.3, is where the actual work is: native net/http and fasthttp handler support, Express-style request and response handlers, HostClient and LBClient in the client package.
v3 is the answer to Fiber's longest-standing objection, that building on fasthttp cuts a project off from the net/http middleware ecosystem. Making both handler styles native reframes Fiber as compatible rather than separate. But rc.3 dates to late 2025 and nothing newer has landed in this feed, while v2 patches keep arriving through August — a long release candidate stretch that leaves users choosing between a stable branch in pure maintenance and a v3 that has not been declared final.
The next meaningful entry is either a v3.0.0 final or a further RC; until one lands, expect the v2 line to continue receiving single-PR backports and security patches.
zip creates and extracts archives from R without depending on external tools. Its 2.x line was incremental — a type column in zip_list(), symlink handling on Unix, hidden shared-library symbols. Version 3.0.0 changed the package's shape by adding password-protected archives and vectorized extraction.
Development is moving from listing and extracting toward parity with what users expect of a general archive utility: encryption schemes including WinZIP AES-256, an encryption column so an archive can be inspected before extraction, and thread counts that respect the session's Ncpus setting. The 3.0.x releases since are consolidation on that new surface.
Expect continued refinement of the encryption and threading paths, with remaining symlink and permission edge cases on Unix the most likely source of the next fixes.
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 Fiber or zip.
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
gargle rebuilt Google auth for R on httr2 and forced the whole wrapper stack to follow
cpp11 has spent two years rebuilding itself on R's supported API surface
callr adds OpenTelemetry tracing, making R subprocess work observable across process boundaries
vctrs 0.7 moved conditional recoding down into the tidyverse type system.
httr2 is growing production concerns: tracing, throttling and token hygiene.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fiber and zip are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. Fiber and zip are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Fiber alternatives in DevOps are ranked by recent ship velocity. Browse the "Fiber alternatives" section above for the current picks, or visit /alternatives/fiber for the full list with editorial commentary on each.
Top zip alternatives in DevOps are ranked by recent ship velocity. Browse the "zip alternatives" section above for the current picks, or visit /alternatives/zip-r for the full list with editorial commentary on each.