simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of assesslite and svines — release velocity, themes, recent moves, and the top alternatives to consider.
Four releases in fifteen hours take causal assumption-checking from resampling to identification
AssessLite attacks the structural assumptions behind a causal finding and returns three-way verdicts — stable, unstable, or not resolvable — feeding proceed, conditional or abstain decisions, with an auditable JSON record validated against a shared schema. It runs natively in R and Python against one spec, with the Python engine reproducing R's coxph(ties=breslow) exactly. The entire 0.1.0-through-0.4.0 arc landed inside a single day in July 2026.
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
AssessLite attacks the structural assumptions behind a causal finding and returns three-way verdicts — stable, unstable, or not resolvable — feeding proceed, conditional or abstain decisions, with an auditable JSON record validated against a shared schema. It runs natively in R and Python against one spec, with the Python engine reproducing R's coxph(ties=breslow) exactly. The entire 0.1.0-through-0.4.0 arc landed inside a single day in July 2026.
The releases are cumulative, each restating the previous feature set and adding to it, so read them as one launch rather than four. The direction across that launch is clear: it started with resampling attacks (permutation, holdout, temporal split, subgroup), turned toward causal identification with declared DAGs and the backdoor criterion, then reached into genuinely dependent data with spatial and interference checks. The correctness work moves in step — the 0.3.0 Bonferroni adjustment fixed a holdout rule that was flagging roughly m times too often with m variants.
The project has repeatedly shipped what it previously listed as future work within days, so the next release most likely converts another declared gap rather than opening a new front.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
This package moves when rvinecopulib moves. The 0.2.4 release exists solely to adapt to a new rvinecopulib version, and 0.2.7 carries auto-generated GitHub release notes with no description at all. It shipped on the same day as kde1d 1.1.1, another package from the same maintainer, which is the pattern to watch: changes in the shared C++ layer surface as near-simultaneous releases across the vine family rather than as independent work.
The next release most plausibly follows another rvinecopulib update rather than adding modelling capability. Two of the three visible entries carry no substantive notes, so this feed will keep underreporting what changed.
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 assesslite or svines.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all assesslite alternatives → · See all svines alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. assesslite and svines are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. assesslite and svines are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top assesslite alternatives in Analytics are ranked by recent ship velocity. Browse the "assesslite alternatives" section above for the current picks, or visit /alternatives/assesslite for the full list with editorial commentary on each.
Top svines alternatives in Analytics are ranked by recent ship velocity. Browse the "svines alternatives" section above for the current picks, or visit /alternatives/svines for the full list with editorial commentary on each.