vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of REDCapR and trackeR — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
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.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
Recent releases track other people's changes: ggmap moving to Stadia maps, gridExtra giving way to patchwork, a cadence field being read into the wrong column. The 2019 entries are where the analysis surface was built out, with cumulative elevation gain, compressed file reading and elevation-noise thresholds, and it has not moved much since.
Expect the next release to be another compatibility or parsing fix rather than a new metric.
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 REDCapR or trackeR.
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.
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.
See all REDCapR alternatives → · See all trackeR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. REDCapR and trackeR 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. REDCapR and trackeR 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 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.
Top trackeR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "trackeR alternatives" section above for the current picks, or visit /alternatives/tracker for the full list with editorial commentary on each.