mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of baseq and dscore — release velocity, themes, recent moves, and the top alternatives to consider.
A basic DNA and RNA sequence toolkit that went quiet for three years, then jumped to 2.0.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
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.
baseq provides elementary sequence processing for biological data in R: cleaning DNA and RNA strings, counting bases and patterns, GC content, translation and reverse complement, and readers and writers for FASTA and FASTQ. The 0.1.x releases all landed in a two-week window in 2023, several of them backfilled within seconds of each other and in an order that does not match their version numbers. A 2.0 tag then appeared in March 2026 after three years of silence, with release notes naming only a development pull request and a CI workflow.
The visible history is a package assembled quickly and then left alone. Across the 0.1.x tags the notes are a printed inventory of exported functions rather than a changelog, with consecutive versions restating the same list unchanged, so the actual increments have to be inferred by diffing those inventories: file-level cleaning and GC content arrived at 0.1.3, and the FASTA and FASTQ readers, writers and converters at 0.1.1. What the 2.0 release contains is not stated anywhere in the feed, which makes the most significant-looking tag here also the least legible.
Nothing in these entries supports a confident prediction. The reappearance of activity after three years and the addition of a CI workflow suggest maintenance has resumed, but until a release describes its own contents there is no basis for saying in what direction.
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 baseq or dscore.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all baseq 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. baseq 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. baseq 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 baseq alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "baseq alternatives" section above for the current picks, or visit /alternatives/baseq 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.