httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of httr and vctrs — release velocity, themes, recent moves, and the top alternatives to consider.
httr's last releases are housekeeping - the package now points users at httr2
httr is in wind-down. The last release with real feature work was 1.4.0 in 2018; everything since is test stabilization, CRAN-driven fixes, and unwinding a dependency on the httpbin service. Version 1.4.7 removed the vignette contents outright and redirects readers to httr2.
vctrs 0.7 moved conditional recoding down into the tidyverse type system.
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
httr is in wind-down. The last release with real feature work was 1.4.0 in 2018; everything since is test stabilization, CRAN-driven fixes, and unwinding a dependency on the httpbin service. Version 1.4.7 removed the vignette contents outright and redirects readers to httr2.
This is a succession, not a decline. The maintainers are keeping httr installable and passing checks for the very large base of packages that depend on it, while all design work happens in httr2. The pattern across these six releases is unambiguous: nothing lands here unless CRAN, a test service, or a platform forced it.
Expect continued patch releases driven only by CRAN checks and toolchain changes; the interesting HTTP work in R will keep landing in httr2.
vctrs defines the type and size rules underpinning the tidyverse. Its 0.6.x line was pure maintenance — CRAN-requested C changes, R-devel test fixes, ALTREP performance. Version 0.7.0 broke that pattern with a family of conditional and recoding functions that duplicate dplyr verbs at lower cost.
The package is absorbing operations that previously lived in dplyr, implementing them once against the shared type rules so every consumer inherits consistent semantics. Releases since have tightened attribute handling in vec_restore() and cleared non-API C usage that R's checking tools now flag.
Expect more tidyverse verbs to acquire vctrs-level implementations, and continued removal of non-API C usage as R narrows what packages are permitted to call.
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 httr or vctrs.
httpuv ships almost nothing, which is what you want from the web server under Shiny
promises drops R6 for plain environments and wires async work into OpenTelemetry
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
htmltools spends three releases walking back its own fill-layout opinions
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. httr and vctrs 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. httr and vctrs 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 httr alternatives in DevOps are ranked by recent ship velocity. Browse the "httr alternatives" section above for the current picks, or visit /alternatives/httr for the full list with editorial commentary on each.
Top vctrs alternatives in DevOps are ranked by recent ship velocity. Browse the "vctrs alternatives" section above for the current picks, or visit /alternatives/vctrs for the full list with editorial commentary on each.