STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A side-by-side editorial comparison of nat.nblast and vahtian — release velocity, themes, recent moves, and the top alternatives to consider.
The NBLAST neuron-similarity engine is stable code on life support, shipping once every few years.
nat.nblast implements NBLAST, the pairwise neuron-morphology similarity algorithm used across the natverse for matching and clustering traced neurons — nblast(), nhclust() and the scoring-matrix machinery around them. The algorithm and its interface have not changed in a decade of releases; recent work is CRAN compliance and build infrastructure.
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.
nat.nblast implements NBLAST, the pairwise neuron-morphology similarity algorithm used across the natverse for matching and clustering traced neurons — nblast(), nhclust() and the scoring-matrix machinery around them. The algorithm and its interface have not changed in a decade of releases; recent work is CRAN compliance and build infrastructure.
The four-year gap between 1.6.6 and 1.6.8 says most of it: this is finished code being kept on CRAN rather than a package under development. The 1.6.8 release fixes Rd cross-references and moves continuous integration to GitHub Actions, with no user-facing change at all. The last release that altered numerical output was 1.6.6 in 2021.
Expect further releases only when CRAN check policy or a natverse dependency forces one. Nothing in these entries suggests algorithmic work is underway.
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 nat.nblast or vahtian.
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
See all nat.nblast 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 nat.nblast alternatives in Analytics are ranked by recent ship velocity. Browse the "nat.nblast alternatives" section above for the current picks, or visit /alternatives/nat-nblast 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.