WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
exametrika vs projoint
A side-by-side editorial comparison of exametrika and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:cranr-package
exametrika vs projoint: at a glance
What is exametrika?
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
exametrika is an R psychometrics package covering IRT, latent class/rank analysis, and biclustering, and it has been shipping features at an unusual clip for a CRAN package. The last two releases stopped adding capability and turned inward: 1.14.0 fixed a documented-but-never-implemented graphical-parameter passthrough, and 1.15.0 landed a full-codebase audit that corrected bugs which silently produced wrong results on missing data and 0-indexed polytomous codes. Argument names, orders, and defaults are now unified across the model functions, with every old name kept working behind a deprecation warning.
What is projoint?
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.
exametrika vs projoint: editorial side-by-side
exametrika
0.0INFRA · APIS
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
◆ Current state
exametrika is an R psychometrics package covering IRT, latent class/rank analysis, and biclustering, and it has been shipping features at an unusual clip for a CRAN package. The last two releases stopped adding capability and turned inward: 1.14.0 fixed a documented-but-never-implemented graphical-parameter passthrough, and 1.15.0 landed a full-codebase audit that corrected bugs which silently produced wrong results on missing data and 0-indexed polytomous codes. Argument names, orders, and defaults are now unified across the model functions, with every old name kept working behind a deprecation warning.
◆ Where it's heading
The arc runs from feature sprawl to consolidation. Through 1.9.0-1.13.0 the package added polytomous biclustering plots, nominal and ordinal IRM samplers, a C++ Gibbs core, and Graphical Lasso; the cost was inconsistent interfaces and correctness bugs that only surfaced under audit. The maintainer is also visibly optimizing for two external gatekeepers — CRAN's 10-minute check budget in 1.13.1, an R Journal reviewer in 1.14.0 — which suggests the package is being groomed for formal publication rather than just iterated on.
◆ Prediction
Expect the next release to continue the deprecation cleanup started in 1.15.0, likely retiring some of the old function names that have carried warnings since 1.7.0, with new modelling work paused until the R Journal submission clears.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to exametrika and projoint
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 exametrika or projoint.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all exametrika alternatives → · See all projoint alternatives →
Recent activity from exametrika and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 1mo agoexametrikaFull-codebase audit fixes silent result corruption, unifies arguments
- 2mo agoexametrikaPlot methods finally forward the graphical parameters they documented
- 3mo agoexametrikaCRAN resubmission: slow tests skipped to fit the check budget
- 3mo agoexametrikaGraphical Lasso and Chatterjee's xi extend the package into network estimation ⚡
- 3mo agoexametrikaFrozen research baseline, never released to CRAN
- 5mo agoexametrikaNominal and ordinal IRM samplers, with generic dispatch by data type
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
Frequently asked questions
What is the difference between exametrika and projoint?
Both compete on the same themes — cran, r-package — within Infra & APIs. 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.
Is exametrika better than projoint?
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.
What are the best alternatives to exametrika?
Top exametrika alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "exametrika alternatives" section above for the current picks, or visit /alternatives/exametrika for the full list with editorial commentary on each.
What are the best alternatives to projoint?
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.