gcube
gcube's recent releases are all packaging metadata, not simulation code
A side-by-side editorial comparison of fillpattern and vahtian — release velocity, themes, recent moves, and the top alternatives to consider.
Pattern fills for ggplot2, hardened against the ways users write sizes
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
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.
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.
Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.
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 fillpattern or vahtian.
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
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 fillpattern alternatives → · See all vahtian alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 fillpattern alternatives in Analytics are ranked by recent ship velocity. Browse the "fillpattern alternatives" section above for the current picks, or visit /alternatives/fillpattern 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.