Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of NGINX and usmap — release velocity, themes, recent moves, and the top alternatives to consider.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
The five preceding releases were security releases: three CVEs in July across both branches, an HTTP/2 and gRPC buffer overflow and an HTTP/3 use-after-free in June. Against that run, 1.31.4 reads as the project returning to feature work, with F5 contributors visible across the stream and upstream changes and four first-time contributors landing fixes. The JSON and data-model libraries are the item worth watching, since general serialization is not something a proxy needs for proxying.
Those libraries have no consumer in this release, so the plausible next move is a feature that uses them, such as structured status output or configuration, rather than another round of parser hardening.
usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.
The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.
Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.
Other Infra & APIs 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 NGINX or usmap.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top NGINX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NGINX alternatives" section above for the current picks, or visit /alternatives/nginx for the full list with editorial commentary on each.
Top usmap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmap alternatives" section above for the current picks, or visit /alternatives/usmap for the full list with editorial commentary on each.