Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of glycoverse and silx — release velocity, themes, recent moves, and the top alternatives to consider.
glycoverse is a meta-package whose whole job is keeping a dozen siblings installable.
glycoverse installs and version-checks the rest of the stack via glycoverse_update(), glycoverse_deps(), and glycoverse_sitrep(). Its releases track membership and distribution rather than capability: glyfun was reclassified as non-core in 0.3.1, the case studies were moved out to a standalone tutorials site in 0.3.2, and 0.2.5 switched installation from GitHub releases to r-universe. No analysis code lives here.
silx settles into maintenance a release after its PySide6 migration
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
glycoverse installs and version-checks the rest of the stack via glycoverse_update(), glycoverse_deps(), and glycoverse_sitrep(). Its releases track membership and distribution rather than capability: glyfun was reclassified as non-core in 0.3.1, the case studies were moved out to a standalone tutorials site in 0.3.2, and 0.2.5 switched installation from GitHub releases to r-universe. No analysis code lives here.
The package is thinning as the ecosystem grows. Documentation moved off to its own site, packages keep shifting between core and non-core, and installation was handed to pak and r-universe rather than bespoke logic. Meanwhile the substantive work in this window happened in the siblings, notably the container migration that reshaped ten of them without requiring a glycoverse release at all.
Expect the next release to be another membership or version-pinning adjustment, most likely acknowledging the newer packages that joined during the container migration.
silx is in the quiet phase after a generational release. 3.1.1 is a single fix to FitWidget loading a fit function from file. The release before it, 3.1.0, was the first real feature work since the migration - asinh axis scaling, twilight colormaps, and dark-theme icons - and 3.0.1 was similarly small. The 3.0.0 cut that reset the Qt binding and Python floor still defines what the line is doing.
The cadence has slowed markedly since April, and the content has shifted from structural change to plotting and colormap refinement. That is the expected shape after a binding migration: downstream beamline code needs a stable target, so the project trades feature velocity for a quiet surface. The gap between 3.0.1 in May and 3.1.0 in August is the clearest signal of the deliberate slowdown.
Expect further point releases servicing the plotting and fitting widgets rather than another structural change, with feature work continuing to arrive in the 3.1.x minors rather than patches.
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 glycoverse or silx.
Omni ships weekly, and almost every week the headline item is an AI feature.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all glycoverse alternatives → · See all silx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. silx 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. silx 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 glycoverse alternatives in Analytics are ranked by recent ship velocity. Browse the "glycoverse alternatives" section above for the current picks, or visit /alternatives/glycoverse for the full list with editorial commentary on each.
Top silx alternatives in Analytics are ranked by recent ship velocity. Browse the "silx alternatives" section above for the current picks, or visit /alternatives/silx for the full list with editorial commentary on each.