← Back to home
Comparison · Infra & APIs

estimatr vs exametrika

A side-by-side editorial comparison of estimatr and exametrika — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

estimatr vs exametrika: at a glance

Featureestimatrexametrika
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescausal-inference, experiments, robust-standard-errors, econometricspsychometrics, irt, biclustering, api-consistency
Last editorial update23h ago1h ago
WebsiteVisit →Visit →

What is estimatr?

Fast design-based estimators for experiments, coasting on CRAN patches.

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

Read the full estimatr trajectory →

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.

Read the full exametrika trajectory →

estimatr vs exametrika: editorial side-by-side

E
estimatr
INFRA · APIS
0.0

Fast design-based estimators for experiments, coasting on CRAN patches.

◆ Current state

estimatr provides the design-based regression estimators the DeclareDesign ecosystem is built on — robust and cluster-robust standard errors, blocked and clustered randomization inference — implemented for speed rather than generality. The last three releases carry no substantive notes: each is a merge commit for a CRAN patch, one of them accompanied by a typo fix.

◆ Where it's heading

Direction cannot be read from this feed. The release notes are unedited merge-commit messages, so the only signal is cadence — roughly annual, each release framed as a CRAN patch rather than as feature work. That pattern is consistent with a package whose estimators are considered finished and which now moves only when CRAN policy requires it.

◆ Prediction

On the evidence here the next release is another CRAN compliance patch, but the notes are too thin to support a confident read of what the maintainers are actually working on.

E
exametrika
INFRA · APIS
0.0

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.

Alternatives to estimatr and exametrika

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 estimatr or exametrika.

See all estimatr alternatives → · See all exametrika alternatives →

Recent activity from estimatr and exametrika

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoexametrikaFull-codebase audit fixes silent result corruption, unifies arguments
  2. 2mo agoexametrikaPlot methods finally forward the graphical parameters they documented
  3. 3mo agoexametrikaCRAN resubmission: slow tests skipped to fit the check budget
  4. 3mo agoexametrikaGraphical Lasso and Chatterjee's xi extend the package into network estimation
  5. 3mo agoexametrikaFrozen research baseline, never released to CRAN
  6. 5mo agoexametrikaNominal and ordinal IRM samplers, with generic dispatch by data type
  7. 1y agoestimatrCRAN version 1.0.4
  8. 2y agoestimatrCRAN version 1.0.2
  9. 3y agoestimatrCRAN version 1.0.0

Frequently asked questions

What is the difference between estimatr and exametrika?

Both compete on the same themes — r-package — within Infra & APIs. estimatr and exametrika 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.

Is estimatr better than exametrika?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. estimatr and exametrika 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.

What are the best alternatives to estimatr?

Top estimatr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "estimatr alternatives" section above for the current picks, or visit /alternatives/estimatr for the full list with editorial commentary on each.

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.