Skip to content
DevUtils Online

Analytics

cube vs uPlot

uPlot leads by 11.2 · clear

A

cube

81.6

21,239 stars · license n/a

B · leads

uPlot

92.8

10,650 stars · MIT

cube versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cube is written mainly in Rust; uPlot is written mainly in JavaScript. The composite score is 81.6 for cube and 92.8 for uPlot.

cube has 21,239 GitHub stars to uPlot's 10,650, a gap of 10,589 (1.99×). Forks are 2,197 for cube and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 80.

Push history: cube was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,189 for cube (0.056 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.

cube is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uPlot is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for cube and 96 for uPlot. This is a procurement signal, not legal advice.

Only uPlot is marked self-hostable here (10,650 stars, deploy score 100). cube is not (21,239 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cube is unpriced in this catalog, uPlot is open source.

The lead is split. cube is furthest ahead on fork community (100 to 80), while uPlot is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

uPlot finishes ahead at 92.8 against cube at 81.6, a 11.2 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

cube versus uPlot metrics
Signal cube uPlot
GitHub stars 21,239 10,650
Forks 2,197 472
Open issues 1,189 132
Adoption 100 93
Activity 100 100
Community 100 80
Issue health 52 84
License 30 96
Self-hosting 35 100
Composite 81.6 92.8

Questions this page answers

Which has more GitHub stars, cube or uPlot?

cube has more GitHub stars: 21,239 versus 10,650 for uPlot. The gap is 10,589 stars.

Which was updated more recently, cube or uPlot?

Both were last pushed on 17 November 2026.

Can I self-host both cube and uPlot?

Only uPlot is marked self-hostable. cube is not.

Which license is easier to embed in a commercial product, cube or uPlot?

cube is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uPlot is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cube vs uPlot score?

uPlot scores 92.8 and cube scores 81.6. This page calls that a clear lead for uPlot.

Related comparisons