rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
A side-by-side editorial comparison of fairmodels and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
fairmodels sits dormant for three years, resurfacing only to satisfy a CRAN check.
fairmodels audits classification models for bias, built around fairness_check() and parity-loss metrics on top of DALEX explainers. The last substantive work dates from 2021; the 2025 release is a single-line change swapping ifelse for if/else in fairness_heatmap. Version 0.2.2 set the package's core design when it superseded metric differences with ratios.
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
fairmodels audits classification models for bias, built around fairness_check() and parity-loss metrics on top of DALEX explainers. The last substantive work dates from 2021; the 2025 release is a single-line change swapping ifelse for if/else in fairness_heatmap. Version 0.2.2 set the package's core design when it superseded metric differences with ratios.
The release history describes a package that reached its intended shape early and has been custodial since — the gap from August 2022 to October 2025 carries no functional change at all. What movement exists is CRAN-driven: documentation compliance, example runtimes, coding-style notes. The fairness metrics themselves have not changed since the parity_loss corrections of 2020.
On this cadence the next release is most likely another CRAN-prompted one-liner rather than new fairness metrics; nothing in these entries points to active development.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
Other Analytics 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 fairmodels or vellum.
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
affiner is quietly turning a grid transformation helper into a small computational geometry library.
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
See all fairmodels alternatives → · See all vellum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 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 Analytics products to evaluate alongside.
Top fairmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "fairmodels alternatives" section above for the current picks, or visit /alternatives/fairmodels for the full list with editorial commentary on each.
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.