Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of ApexCharts and hubUtils — release velocity, themes, recent moves, and the top alternatives to consider.
Licensing settled, ApexCharts is back to changing what a chart can take as input.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
The hubverse's shared plumbing, tracking schema versions and converting output types.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
The through-line now is input and arrangement rather than catalogue size. Charts increasingly accept the measurements a team actually has instead of pre-aggregated values, and the seams that let you hand a chart its own layout — plotOptions.unit.positions, the pluggable layout hook — are being filled in with kits rather than hard-coded options. The premium boundary has stopped moving; the free catalogue keeps growing around it.
Expect the raw-observation pattern to reach another chart type now that the bar pathway handles binning, and expect the remaining pluggable seams to get companion kits the way positions just did.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
The through-line is that this package absorbs whatever the schema is doing — v5, then v6 with target-data configuration, each arriving with matching accessors and example hubs so the sibling packages can be tested against something real. convert_output_type() is the one piece of genuine computation here, and it has now been optimised by roughly an order of magnitude, suggesting it is being used at scales the original implementation did not anticipate. Everything else is accessors and fixtures.
Expect the next substantive release to track the next hubverse schema version, with any independent work concentrated on convert_output_type(), the only performance-sensitive function in the package.
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 ApexCharts or hubUtils.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
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.
See all ApexCharts alternatives → · See all hubUtils alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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 ApexCharts alternatives in Analytics are ranked by recent ship velocity. Browse the "ApexCharts alternatives" section above for the current picks, or visit /alternatives/apexcharts for the full list with editorial commentary on each.
Top hubUtils alternatives in Analytics are ranked by recent ship velocity. Browse the "hubUtils alternatives" section above for the current picks, or visit /alternatives/hubutils for the full list with editorial commentary on each.