TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of churon and vahtian — release velocity, themes, recent moves, and the top alternatives to consider.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
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.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.
Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.
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 churon or vahtian.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all churon 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 churon alternatives in Analytics are ranked by recent ship velocity. Browse the "churon alternatives" section above for the current picks, or visit /alternatives/churon 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.