A · leads
excelize
97.5
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 13.7 · clear
A · leads
97.5
21,136 stars · BSD-3-Clause
B
83.8
23,865 stars · license n/a
excelize versus timescaledb 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; timescaledb is written mainly in C. The composite score is 97.5 for excelize and 83.8 for timescaledb.
timescaledb has 23,865 GitHub stars to excelize's 21,136, a gap of 2,729 (1.13×). Forks are 2,004 for excelize and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 93.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 476 for timescaledb (0.020 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. timescaledb 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. License scores in this pair are 96 for excelize and 30 for timescaledb. This is a procurement signal, not legal advice.
Only excelize is marked self-hostable here (21,136 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: excelize is open source, timescaledb is unpriced in this catalog.
The lead is split. excelize is furthest ahead on license flexibility (96 to 30), while timescaledb is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.5 against timescaledb at 83.8, a 13.7 point clear 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 | timescaledb |
|---|---|---|
| GitHub stars | 21,136 | 23,865 |
| Forks | 2,004 | 1,188 |
| Open issues | 176 | 476 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 84 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.5 | 83.8 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 21,136 for excelize. The gap is 2,729 stars.
Both were last pushed on 17 November 2026.
Only excelize is marked self-hostable. timescaledb is not.
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. timescaledb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
excelize scores 97.5 and timescaledb scores 83.8. This page calls that a clear lead for excelize.