rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
radiatR vs Volatility
A side-by-side editorial comparison of radiatR and Volatility — release velocity, themes, recent moves, and the top alternatives to consider.
radiatR vs Volatility: at a glance
What is radiatR?
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
What is Volatility?
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.
radiatR vs Volatility: editorial side-by-side
radiatR
2.5INFRA · APIS
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
◆ Current state
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
◆ Where it's heading
Three releases in twelve days show a package hardening in public rather than accreting features. The direction of travel is toward refusing bad input instead of quietly working around it: non-finite coordinate rows now error by default rather than being dropped silently, combining Tracks objects rejects colliding trajectory ids and conflicting calibration metadata instead of merging them and discarding one side, and the Shiny app clears prior state before reading a new upload. The statistical surface is growing in parallel, but within the scope the first release already claimed.
◆ Prediction
Expect the remaining goodness-of-fit gap the notes name explicitly, Jones-Pewsey, to be filled in a later release, and the error-on-bad-input treatment to reach the parts of the loader it has not yet covered. A CRAN submission is the natural next step for a package this young, though nothing in these entries commits to one.
Volatility
0.0INFRA · APIS
Volatility 3 caught up with Volatility 2, then started reorganising itself.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to radiatR and Volatility
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 radiatR or Volatility.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all radiatR alternatives → · See all Volatility alternatives →
Recent activity from radiatR and Volatility
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoradiatRctrax loader dropped; bad coordinates now error by default
- 1mo agoradiatRWrapped-Cauchy and Pycke tests close two statistical gaps
- 1mo agoradiatRFirst public release ⚡
- 3mo agoVolatility2.28.0 adds sockscan and process_spoofing, improves Intel scanning
- 6mo agoVolatility2.27.0 adds an arrow/parquet renderer and pebmasquerade
- 10mo agoVolatility2.26.2 moves malware plugins into their own namespace ⚡
- 1y agoVolatility2.26.0 reaches functional parity with Volatility 2 ⚡
- 1y agoVolatility2.11.0 adds fifteen plugins and raises the Python floor to 3.8
- 1y agoVolatility2.8.0 adds vmscan and a batch of Windows injection plugins
Frequently asked questions
What is the difference between radiatR and Volatility?
They serve adjacent needs but don't currently overlap on shipped themes. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is radiatR better than Volatility?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to radiatR?
Top radiatR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "radiatR alternatives" section above for the current picks, or visit /alternatives/radiatr for the full list with editorial commentary on each.
What are the best alternatives to Volatility?
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.