vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of basictabler and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Four years dormant, then a CRAN-notes patch — the table renderer that already did what it set out to do.
basictabler renders arbitrary tables to HTML, Excel and, since 2021, Word, PowerPoint and PDF. It is the simpler sibling of pivottabler by the same maintainer, and the two are deliberately kept API-compatible. The package went silent after June 2021 and returned in April 2025 with 1.0.4, a release that exists only to clear CRAN notes — 48 characters of release note for four years of elapsed time.
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
basictabler renders arbitrary tables to HTML, Excel and, since 2021, Word, PowerPoint and PDF. It is the simpler sibling of pivottabler by the same maintainer, and the two are deliberately kept API-compatible. The package went silent after June 2021 and returned in April 2025 with 1.0.4, a release that exists only to clear CRAN notes — 48 characters of release note for four years of elapsed time.
The pre-silence arc is a package converging on its sibling. 0.3.0 switched header cells to th elements specifically because pivottabler already did; 1.0.0 changed findCells() matching semantics for the same reason, and introduced value-driven styling; 1.0.2 outsourced Word, PowerPoint and PDF output to flextabler rather than implementing them. Each move either aligned with pivottabler or delegated to someone else, which is how a package reaches a state where four years pass without a feature.
Nothing in the feed suggests feature work resuming; expect maintenance releases only, arriving when CRAN checks or a change in pivottabler force one.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
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 basictabler or surveycore.
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 basictabler alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. basictabler and surveycore 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. basictabler and surveycore 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 basictabler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "basictabler alternatives" section above for the current picks, or visit /alternatives/basictabler for the full list with editorial commentary on each.
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.