← Back to home
Comparison · Infra & APIs

dscore vs exametrika

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

Shared themes:psychometricsr-package

dscore vs exametrika: at a glance

Featuredscoreexametrika
SectorInfra & APIsInfra & APIs
Velocity score0.03.8
Sparks · 30d01
Top themeschild-development, psychometrics, global-health, r-packagepsychometrics, irt, biclustering, breaking-change
Last editorial update1d ago16h ago
WebsiteVisit →Visit →

What is dscore?

The D-score reference implementation rebuilt its measurement foundation on seven countries.

dscore computes the D-score and DAZ, the GSED developmental measurement used in child-health research, and it is the reference implementation rather than one option among several. The package is at 2.1.0 after a dense 2025: the default key moved from three-country to seven-country validation data, the licence moved from AGPL to Apache 2.0, and the 2.1.0 line added per-country references, full BSID-III coverage and domain-level scoring. Breaking changes are routine here and always come with a documented fallback key or algorithm argument.

Read the full dscore trajectory →

What is exametrika?

exametrika breaks its own numbers to fix them, and ships the fit statistic nominal data lacked.

exametrika is an R psychometrics package covering IRT, latent class and rank analysis, and biclustering. Version 2.0.0 is a deliberate break: an EM convergence defect inherited from the reference implementation stopped estimation after as little as one cycle while reporting convergence, so every EM-based model in the package now returns different estimates than it did before. The package no longer reproduces the numbers printed in Shojima (2022), and the maintainer says so directly rather than burying it. The deprecation removals promised since 1.15.0 ride along in the same release, and the package title changed to Test Data Engineering.

Read the full exametrika trajectory →

dscore vs exametrika: editorial side-by-side

D
dscore
INFRA · APIS
0.0

The D-score reference implementation rebuilt its measurement foundation on seven countries.

◆ Current state

dscore computes the D-score and DAZ, the GSED developmental measurement used in child-health research, and it is the reference implementation rather than one option among several. The package is at 2.1.0 after a dense 2025: the default key moved from three-country to seven-country validation data, the licence moved from AGPL to Apache 2.0, and the 2.1.0 line added per-country references, full BSID-III coverage and domain-level scoring. Breaking changes are routine here and always come with a documented fallback key or algorithm argument.

◆ Where it's heading

The arc runs from correcting the instrument to broadening who can use it. The 2020-2024 releases were item-table repair and error correction, including a scale-factor bug that altered published standard errors; from 1.11.0 onward the work is distribution — a permissive licence, more instruments mapped in, and references resolved per country rather than pooled. That combination points at national-survey and app-embedded use rather than research-only use.

◆ Prediction

The 2.0.0 notes state that groundwork was laid for extending D-scores to older children, and 2.0.0 still tells users to fall back to gsed2406 for instruments outside GSED SF and LF. Expect the next releases to close that gap by mapping more instruments into gsed2510, with the older-age extension the likeliest headline feature.

E
exametrika
INFRA · APIS
3.8

exametrika breaks its own numbers to fix them, and ships the fit statistic nominal data lacked.

◆ Current state

exametrika is an R psychometrics package covering IRT, latent class and rank analysis, and biclustering. Version 2.0.0 is a deliberate break: an EM convergence defect inherited from the reference implementation stopped estimation after as little as one cycle while reporting convergence, so every EM-based model in the package now returns different estimates than it did before. The package no longer reproduces the numbers printed in Shojima (2022), and the maintainer says so directly rather than burying it. The deprecation removals promised since 1.15.0 ride along in the same release, and the package title changed to Test Data Engineering.

◆ Where it's heading

The consolidation arc that ran through 1.14.0 and 1.15.0 has closed, but not the way the audit trail suggested it would. Rather than pausing new modelling work through the cleanup, 2.0.0 pairs the breaking removals with real capability: M2() and add_M2() bring a limited-information fit statistic with a full margin-based index set, order-restricted estimation becomes the default for Ranklustering on the strength of a higher likelihood, and LCA() picks up nominal and rated data. The correctness fixes share one shape - defects that got worse as data got larger, where a 700-respondent dataset silently merged fields and a 40-item test returned no assignments at all. A two-tier test suite now keeps 3,507 tests in CI while CRAN sees a 17-second subset.

◆ Prediction

With the deprecation backlog cleared and the EM core rewritten, the next releases have room to build on M2() - most plausibly extending the margin-based indices to the models that do not yet report them. Whether the R Journal submission that shaped 1.13.1 and 1.14.0 has landed is not visible in these entries.

Alternatives to dscore 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 dscore or exametrika.

See all dscore alternatives → · See all exametrika alternatives →

Recent activity from dscore and exametrika

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

  1. 1d agoexametrikaEM convergence fix changes every estimate; deprecated names removed
  2. 1mo agoexametrikaFull-codebase audit fixes silent result corruption, unifies arguments
  3. 2mo agoexametrikaPlot methods finally forward the graphical parameters they documented
  4. 3mo agoexametrikaCRAN resubmission: slow tests skipped to fit the check budget
  5. 3mo agoexametrikaGraphical Lasso and Chatterjee's xi extend the package into network estimation
  6. 3mo agoexametrikaFrozen research baseline, never released to CRAN
  7. 7mo agodscoredscore 2.1.0
  8. 10mo agodscoredscore 2.0.0
  9. 10mo agodscoredscore 1.11.0
  10. 1y agodscoredscore 1.10.0
  11. 2y agodscoredscore 1.9.0
  12. 3y agodscoredscore 1.7.0

Frequently asked questions

What is the difference between dscore and exametrika?

Both compete on the same themes — psychometrics, r-package — within Infra & APIs. exametrika is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 dscore better than exametrika?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. exametrika is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 dscore?

Top dscore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dscore alternatives" section above for the current picks, or visit /alternatives/dscore 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.