vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of dialr and REDCapR — 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.
The REDCap API client finished its breaking cleanup and settled into CRAN-compliance mode.
REDCapR is a mature R client for the REDCap research data-capture API, and its release stream shows a package that has already made its consequential changes. The last two releases (1.5.0, 1.6.0) exist purely to satisfy CRAN checks — dropping native pipes from non-essential code, keeping examples from touching an external server. The functional surface has been stable since early 2025.
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.
REDCapR is a mature R client for the REDCap research data-capture API, and its release stream shows a package that has already made its consequential changes. The last two releases (1.5.0, 1.6.0) exist purely to satisfy CRAN checks — dropping native pipes from non-essential code, keeping examples from touching an external server. The functional surface has been stable since early 2025.
The arc runs from a deliberate interface break in 1.2.0 — read functions returning tibbles, the *_collapsed parameter family deprecated — through 1.4.0 broadening API coverage into REDCap's file repository, and then into pure maintenance. Test infrastructure has been getting more attention than features: a redirection layer so users can point the suite at their own server, a multilevel-model test project. That is the signature of a package whose maintainer is defending stability rather than expanding scope.
Expect continued CRAN-compliance releases at roughly quarterly cadence; any new feature work is most likely further coverage of REDCap endpoints the package does not yet wrap, following the file-repository pattern.
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 REDCapR.
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.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
One paper, one release: the functional control chart package ships methods as they get published.
See all dialr alternatives → · See all REDCapR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. dialr and REDCapR 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 REDCapR 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 REDCapR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "REDCapR alternatives" section above for the current picks, or visit /alternatives/redcapr for the full list with editorial commentary on each.