Skip to content
DevUtils Online

Analytics

cube vs excelize

excelize leads by 16.2 · decisive

A

cube

81.6

21,239 stars · license n/a

B · leads

excelize

97.8

21,136 stars · BSD-3-Clause

cube versus excelize 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; excelize is written mainly in Go. The composite score is 81.6 for cube and 97.8 for excelize.

cube has 21,239 GitHub stars to excelize's 21,136, a gap of 103 (1.00×). Forks are 2,197 for cube and 2,004 for excelize. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 99.

Push history: cube was last pushed on 17 November 2026 (0 days ago), and excelize was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,189 for cube (0.056 per star) and 176 for excelize (0.008 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. excelize is listed as BSD-3-Clause, 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 excelize. This is a procurement signal, not legal advice.

Only excelize is marked self-hostable here (21,136 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, excelize is open source.

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

excelize finishes ahead at 97.8 against cube at 81.6, a 16.2 point decisive 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 excelize metrics
Signal cube excelize
GitHub stars 21,239 21,136
Forks 2,197 2,004
Open issues 1,189 176
Adoption 100 100
Activity 100 100
Community 100 99
Issue health 52 84
License 30 96
Self-hosting 35 100
Composite 81.6 97.8

excelize

Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cube or excelize?

cube has more GitHub stars: 21,239 versus 21,136 for excelize. The gap is 103 stars.

Which was updated more recently, cube or excelize?

Both were last pushed on 17 November 2026.

Can I self-host both cube and excelize?

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

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

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. excelize is listed as BSD-3-Clause, 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 excelize score?

excelize scores 97.8 and cube scores 81.6. This page calls that a decisive lead for excelize.

Related comparisons