← Back to home
Comparison · Infra & APIs

dscore vs slendr

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

dscore vs slendr: at a glance

Featuredscoreslendr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themeschild-development, psychometrics, global-health, r-packagepopulation-genetics, simulation, tree-sequences, python-interop
Last editorial update46m ago5h 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 slendr?

Population-genetic simulation in R, opened up to selection and finally easier to install.

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

Read the full slendr trajectory →

dscore vs slendr: 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.

S
slendr
INFRA · APIS
0.0

Population-genetic simulation in R, opened up to selection and finally easier to install.

◆ Current state

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

◆ Where it's heading

Since the 1.0.0 release added non-neutral simulation, the work has shifted from capability to friction. A large share of recent notes concerns Python environment handling, conda activation races on Windows, dependency pruning that made shiny optional, and argument names that misled users, as when gene_flow()'s rate argument turned out to mean total ancestry proportion rather than a rate. That is the profile of a package whose scientific surface is settled and whose remaining problems are the ones users actually hit.

◆ Prediction

Expect the uv-based environment path to move from fallback to default once it has proven itself, given the notes already describe an environment variable for making it so. The deprecated rate argument in gene_flow() is explicitly slated for removal in a future major release, which is the clearest signal here of what a 2.0 would contain.

Alternatives to dscore and slendr

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 slendr.

See all dscore alternatives → · See all slendr alternatives →

Recent activity from dscore and slendr

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

  1. 1mo agoslendrEphemeral uv Python environments remove the setup step
  2. 7mo agodscoredscore 2.1.0
  3. 7mo agoslendrgene_flow() separates migration rate from ancestry proportion
  4. 9mo agoslendrshiny made optional; SLiM 5.1 and Python 3.13 required
  5. 10mo agodscoredscore 2.0.0
  6. 10mo agodscoredscore 1.11.0
  7. 1y agoslendrconda activation reverted to a slower but reliable path
  8. 1y agodscoredscore 1.10.0
  9. 1y agoslendrBackends raised to SLiM 5.0, tskit 0.6.4 and msprime 1.3.4
  10. 1y agoslendrNon-neutral models arrive; slim() interface simplified
  11. 2y agodscoredscore 1.9.0
  12. 3y agodscoredscore 1.7.0

Frequently asked questions

What is the difference between dscore and slendr?

They serve adjacent needs but don't currently overlap on shipped themes. dscore and slendr 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 dscore better than slendr?

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

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