mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of melodi and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
INSEE's statistics API gets a French R client that keeps meeting its edge cases
Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.
The work is convergence with an API that is still moving. Version 0.3.0 added label lookups so codes become readable; 1.0.0 centralised configuration; 1.0.1 and 1.0.2 each fix a place where a real dataset does not match the assumed shape — get_range_geo() needing an extra label field, then the consumer price index series naming its value column differently from every other dataset. Release notes are in French, which is consistent with the audience.
The 1.0.x pattern is one dataset-shape exception per release, which suggests the client is still discovering how much the Melodi datasets vary rather than converging on a general parser. Expect more of the same until the variation is handled generically.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
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 melodi or surveycore.
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 melodi alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. melodi and surveycore 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. melodi and surveycore 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 melodi alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "melodi alternatives" section above for the current picks, or visit /alternatives/melodi for the full list with editorial commentary on each.
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.