Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of dialr and usmap — release velocity, themes, recent moves, and the top alternatives to consider.
The R phone-number package stopped only parsing numbers and started asking them where they are.
dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.
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.
dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.
Two forces shape the history. One is expansion into what libphonenumber knows beyond the number itself — carrier, geocode, timezone — which happened once, in 2019, and has not been extended since. The other is the ongoing cost of being a Java wrapper inside an R tidyverse: rJava initialisation moved so the :: form works, phone vectors reclassified when tibble 3.0.0 changed how it treats list-based classes, and repeated performance work to make crossing the Java boundary tolerable. The maintainer has floated moving the phone class onto vctrs but has not.
The vctrs migration is the one change the maintainer has explicitly signalled, and the hard-deprecated one-shot functions were slated for removal in the next major release; three years of silence make neither imminent.
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 dialr or usmap.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
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.
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. dialr and usmap 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. dialr and usmap 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 Infra & APIs products to evaluate alongside.
Top dialr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dialr alternatives" section above for the current picks, or visit /alternatives/dialr 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.