vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of metagroup and REDCapR — release velocity, themes, recent moves, and the top alternatives to consider.
A first release that turns meta-analytic heterogeneity into interpretable subgroups.
metagroup reached CRAN in late August with a complete first release: eight grouping functions covering binary, continuous, correlational, proportion, incidence and generic inverse-variance data, plus interpretation and plotting on top. The two releases since are CRAN review housekeeping. The package has shipped nothing but its launch.
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.
metagroup reached CRAN in late August with a complete first release: eight grouping functions covering binary, continuous, correlational, proportion, incidence and generic inverse-variance data, plus interpretation and plotting on top. The two releases since are CRAN review housekeeping. The package has shipped nothing but its launch.
The design is a two-step pipeline, partitioning studies into homogeneous clusters and then characterising what those clusters have in common, which puts interpretation rather than detection at the centre. The follow-up releases suggest the author is still clearing the CRAN intake process rather than extending the method.
The next substantive release most likely broadens the interpretation side, since the grouping functions already cover the standard effect-size types.
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 metagroup or REDCapR.
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 metagroup alternatives → · See all REDCapR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. metagroup 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. metagroup 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 metagroup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "metagroup alternatives" section above for the current picks, or visit /alternatives/metagroup 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.