WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of inti and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
inti keeps compounding small statistics and publishing tools for plant-science labs.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
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.
inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.
Two axes are moving. Analysis is deepening inside Yupana, where PCA went from a single view to a sub-module with its own contribution and correlation outputs across three tags. Publishing is widening around rticle() and scihub(), which now handle Google Docs markdown, crossrefs and page numbers, continuing the gdocs2qmd work from the 0.6 line. Neither is a change of direction; the package accretes features where the maintainer's own research workflow needs them.
Expect the next tag to extend the PCA sub-module again and add another rticle() or scihub() rendering detail, on the two-to-six-week cadence the 0.7 line has held.
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 inti 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 inti alternatives → · See all projoint alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. inti and projoint are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. inti and projoint are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top inti alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inti alternatives" section above for the current picks, or visit /alternatives/inti 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.