mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of massProps and Volatility — release velocity, themes, recent moves, and the top alternatives to consider.
A mass-properties rollup spends a year on documentation and follows its sibling's API
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.
massProps computes mass, centre of mass and inertia tensors — and their uncertainties — over tree-structured assemblies, the calculation systems engineers run on a spacecraft or vehicle breakdown. It sits on top of rollupTree, the same author's generic recursive-computation engine, and its most recent release exists only to adopt accessor functions that sibling added two weeks earlier.
Every release in the window is documentation, benchmarks, or keeping in step with rollupTree. The inertia tensor and radius-of-gyration uncertainty equations have been reformatted and re-explained three separate times, which suggests the hard part of this package is not the computation but making the covariance treatment legible to the engineers meant to trust it. Development effort clearly sits in the engine underneath, not here.
The pattern is unambiguous: rollupTree ships an API change and massProps follows within a fortnight. Whatever the engine does next is what appears here next, and on this evidence it will arrive as a one-line release note.
The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.
Two things are happening at once. The plugin catalogue keeps growing on the Linux side in particular — tracing, kallsyms, ftrace, VMA scanning, smearing protection — reflecting where memory forensics currently has the least coverage. And the framework is being made into something other tools consume: structured output formats, a shipped Windows executable, a namespaced plugin taxonomy with a year-long deprecation window. The project is treating plugin names as an interface it owes users stability on.
Expect the malware namespace migration to complete as the deprecated names age out, and the Linux plugin surface to keep taking the bulk of new additions, with output-format work continuing to open the framework to automated pipelines.
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 massProps or Volatility.
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 massProps alternatives → · See all Volatility alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. massProps and Volatility 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. massProps and Volatility 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 massProps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "massProps alternatives" section above for the current picks, or visit /alternatives/massprops for the full list with editorial commentary on each.
Top Volatility alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Volatility alternatives" section above for the current picks, or visit /alternatives/volatility for the full list with editorial commentary on each.