WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of covr and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
covr's coverage tooling has been stable to the point of dormancy since 2022
covr is the de facto R code-coverage package, and its visible release history stops at 3.6.0 in August 2022. That release was the last substantive one: an opt-in test-trace recorder, a permissive MIT relicense, Google Cloud Build support, and a long list of robustness fixes. Everything before it is a slow cadence of CI-integration additions and check failures.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
covr is the de facto R code-coverage package, and its visible release history stops at 3.6.0 in August 2022. That release was the last substantive one: an opt-in test-trace recorder, a permissive MIT relicense, Google Cloud Build support, and a long list of robustness fixes. Everything before it is a slow cadence of CI-integration additions and check failures.
The arc is a tool that reached feature-completeness for its niche and then stopped moving. The direction of travel while it was active was integration breadth — Codecov, Coveralls, GitHub Actions, SonarQube, Google Cloud Build — rather than deeper analysis. With no releases since 2022, the practical trajectory is that covr is maintained by its ecosystem position, not by shipping.
The entries do not support a confident prediction about the next release; there has been no visible activity in this feed for roughly four years, so the honest read is that covr is in caretaker mode.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
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 covr or projoint.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all covr alternatives → · See all projoint alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top covr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "covr alternatives" section above for the current picks, or visit /alternatives/covr for the full list with editorial commentary on each.
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.