A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 5.0 · narrow
A · leads
97.9
21,136 stars · BSD-3-Clause
B
92.9
10,650 stars · MIT
excelize versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. excelize is written mainly in Go; uPlot is written mainly in JavaScript. The composite score is 97.9 for excelize and 92.9 for uPlot.
excelize has 21,136 GitHub stars to uPlot's 10,650, a gap of 10,486 (1.98×). Forks are 2,004 for excelize and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 81.
Push history: excelize 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 176 for excelize (0.008 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. 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 96 for excelize and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and uPlot (10,650 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: excelize is open source, uPlot is open source.
excelize is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 19 points (100 vs 81), and the tightest is self-hosting at 0 points (100 vs 100).
excelize finishes ahead at 97.9 against uPlot at 92.9, a 5.0 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | excelize | uPlot |
|---|---|---|
| GitHub stars | 21,136 | 10,650 |
| Forks | 2,004 | 472 |
| Open issues | 176 | 132 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 92.9 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
📈 A small, fast chart for time series, lines, areas, ohlc & bars
excelize has more GitHub stars: 21,136 versus 10,650 for uPlot. The gap is 10,486 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
excelize scores 97.9 and uPlot scores 92.9. This page calls that a narrow lead for excelize.