vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of DMRnet and dscore — release velocity, themes, recent moves, and the top alternatives to consider.
A categorical-variable selection package that publishes its full test logs as release candidates.
DMRnet implements delete-or-merge-regressors model selection for high-dimensional categorical data, alongside SOSnet and GLAMER variants from the same research group. Development is slow and academic — 0.4.0 in 2023, then two years to 0.4.1 in August 2025, which corrects an invalid lambda.1se computation and the cross-validation plots that displayed it. Every real release is preceded days earlier by a release-candidate entry containing the raw output of the correctness and consistency test suite.
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.
DMRnet implements delete-or-merge-regressors model selection for high-dimensional categorical data, alongside SOSnet and GLAMER variants from the same research group. Development is slow and academic — 0.4.0 in 2023, then two years to 0.4.1 in August 2025, which corrects an invalid lambda.1se computation and the cross-validation plots that displayed it. Every real release is preceded days earlier by a release-candidate entry containing the raw output of the correctness and consistency test suite.
The package is converging on correctness rather than expanding. 0.3.3 was a wall of fixes to inference, log-likelihood, and degenerate cross-validation cases; 0.4.0 added the var_sel algorithm and brought GLAMER into the package's own net idiom over its tau parameter; 0.4.1 is again a statistical correctness fix. The published test-log releases are the tell — this maintainer treats reproducible evidence that hard cases still pass as part of the release artifact, which is unusual outside academic statistical software.
Given the two-year gap before 0.4.1 and its narrow scope, the next release is most likely another correctness fix arriving on a multi-year cadence, again preceded by a full test-log release candidate.
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.
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.
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.
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 DMRnet or dscore.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all DMRnet alternatives → · See all dscore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. DMRnet and dscore 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DMRnet and dscore 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.
Top DMRnet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DMRnet alternatives" section above for the current picks, or visit /alternatives/dmrnet for the full list with editorial commentary on each.
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.