rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of melodi and mpactr — 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.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
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.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
The package is stabilizing its input contract rather than growing its filtering methods. Metadata column names are now forced lowercase inside import_data() regardless of how the file was written, imported peak_tables names not present in the injection column are lowercased too, and get_meta_data() was renamed to get_metadata() in the same pass. Before that the work was infrastructural — Rcpp introduced to speed up filtering, data.table moved from Depends to Imports, and memory errors cleared so the package passes Valgrind and both sanitizers. Note the earliest entry compares against a v1.0.0 tag that precedes 0.1.0 in the repository, so version ordering in this feed is not reliable.
The case-normalization work has now touched both metadata columns and peak table names across two consecutive releases, which suggests the input-matching problem is not fully closed and a third pass is plausible. Nothing in these entries points to new filtering methods.
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 mpactr.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all melodi alternatives → · See all mpactr 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 mpactr 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 mpactr 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 mpactr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mpactr alternatives" section above for the current picks, or visit /alternatives/mpactr for the full list with editorial commentary on each.