nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
A side-by-side editorial comparison of lstar and UCell — release velocity, themes, recent moves, and the top alternatives to consider.
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
UCell scores gene signatures in single-cell data using a rank-based metric that is robust to dataset composition. Its release history reads as a sequence of ecosystem accommodations: Bioconductor submission in 2.0, SmoothKNN() for k-nearest-neighbor smoothing of scores in 2.2, smoothing applied directly to expression slots in 2.4, Seurat v5 assay compatibility in 2.6, multi-layer Seurat v5 objects in 2.8, and a missing_genes parameter in 2.14 that lets callers impute or skip signature genes absent from the data. Version 2.16 tracks Bioconductor 3.23 and points at a new publication and a Python implementation, pyUCell.
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
UCell scores gene signatures in single-cell data using a rank-based metric that is robust to dataset composition. Its release history reads as a sequence of ecosystem accommodations: Bioconductor submission in 2.0, SmoothKNN() for k-nearest-neighbor smoothing of scores in 2.2, smoothing applied directly to expression slots in 2.4, Seurat v5 assay compatibility in 2.6, multi-layer Seurat v5 objects in 2.8, and a missing_genes parameter in 2.14 that lets callers impute or skip signature genes absent from the data. Version 2.16 tracks Bioconductor 3.23 and points at a new publication and a Python implementation, pyUCell.
Two threads run through this. The scoring algorithm itself has barely changed — the rank-based core is stable, and 2.14's reformatting to gene indices rather than string matching is a speed change, not a method change. What does change constantly is object-format compatibility, which is the tax of living between Seurat and SingleCellExperiment. The pyUCell reference in 2.16 is the first sign of the method reaching beyond R, though these notes say nothing about its scope.
The cadence is locked to Bioconductor's twice-yearly release train, so the next version will most likely accompany Bioconductor 3.24 with whatever Seurat or SingleCellExperiment changes it brings.
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 lstar or UCell.
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.
Top UCell alternatives in Analytics are ranked by recent ship velocity. Browse the "UCell alternatives" section above for the current picks, or visit /alternatives/ucell for the full list with editorial commentary on each.