fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of cubist and vahtian — release velocity, themes, recent moves, and the top alternatives to consider.
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
Cubist is the R interface to Quinlan's rule-based regression model, wrapping the original C sources behind an R API and feeding the tidymodels rules package. The 0.6.0 release adds a strip_time_stamps control that removes date, time and duration information from model output, and now errors rather than silently misbehaving when a date or date-time column is passed. Error reporting moves from base stop() and warning() to cli.
A provenance-first corpus tool hands its verification core to agents over MCP
vahtian freezes a set of research records into a content-hashed, date-locked corpus, verifies it is untampered, and keeps a hash-chained audit ledger. It ships in Python and R with byte-identical content hashes enforced by a golden-hash test in both suites. In five weeks it went from first release to exposing its five core operations through a local stdio MCP server and registering in the MCP Registry.
Cubist is the R interface to Quinlan's rule-based regression model, wrapping the original C sources behind an R API and feeding the tidymodels rules package. The 0.6.0 release adds a strip_time_stamps control that removes date, time and duration information from model output, and now errors rather than silently misbehaving when a date or date-time column is passed. Error reporting moves from base stop() and warning() to cli.
The direction is custodial: this is a mature algorithm with a stable definition, so the work is making a decades-old C codebase behave predictably inside a modern R workflow. The reproducibility thread is the clearest one — embedded timestamps mean two identical models compare as different objects, which breaks caching, testing and any workflow that hashes results. Alongside it runs slow C hygiene, from keyword symbol overwrites in 0.5.0 to unused-variable warnings in 0.6.0.
Expect continued small maintenance releases tracking CRAN compiler requirements and the needs of the rules package, with no change to the modelling algorithm itself.
vahtian freezes a set of research records into a content-hashed, date-locked corpus, verifies it is untampered, and keeps a hash-chained audit ledger. It ships in Python and R with byte-identical content hashes enforced by a golden-hash test in both suites. In five weeks it went from first release to exposing its five core operations through a local stdio MCP server and registering in the MCP Registry.
The direction is explicit in the project's own framing — human-first, AI-second, auditable — and the MCP server is what makes that framing operational rather than rhetorical. Rather than adding judgement, the tool is being positioned as the thing an agent calls to prove a corpus has not moved. The CiteVahti claim-source comparator, mirrored across both languages under a parity gate, extends the same idea to per-claim checking. Everything stays on the user's machine: no accounts, no telemetry.
The comparator's per-field epistemic states are the newest and least settled piece; expect the next release to extend those states or to widen the R package's distribution, which is still described as coming.
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 cubist or vahtian.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
See all cubist alternatives → · See all vahtian alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — reproducibility — within Analytics. vahtian is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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. vahtian is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 cubist alternatives in Analytics are ranked by recent ship velocity. Browse the "cubist alternatives" section above for the current picks, or visit /alternatives/cubist for the full list with editorial commentary on each.
Top vahtian alternatives in Analytics are ranked by recent ship velocity. Browse the "vahtian alternatives" section above for the current picks, or visit /alternatives/vahtian for the full list with editorial commentary on each.