A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 10.3 · clear
A · leads
97.9
21,136 stars · BSD-3-Clause
B
87.6
13,328 stars · AGPL-3.0
excelize versus rybbit 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; rybbit is written mainly in TypeScript. The composite score is 97.9 for excelize and 87.6 for rybbit.
excelize has 21,136 GitHub stars to rybbit's 13,328, a gap of 7,808 (1.59×). Forks are 2,004 for excelize and 791 for rybbit. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 88.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and rybbit was last pushed on 13 November 2026 (4 days ago). Open issues stand at 176 for excelize (0.008 per star) and 212 for rybbit (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 92.
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. rybbit is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for excelize and 52 for rybbit. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and rybbit (13,328 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, rybbit is open source.
excelize is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
excelize finishes ahead at 97.9 against rybbit at 87.6, a 10.3 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 | rybbit |
|---|---|---|
| GitHub stars | 21,136 | 13,328 |
| Forks | 2,004 | 791 |
| Open issues | 176 | 212 |
| Adoption | 100 | 95 |
| Activity | 100 | 92 |
| Community | 100 | 88 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.6 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
excelize has more GitHub stars: 21,136 versus 13,328 for rybbit. The gap is 7,808 stars.
excelize was pushed more recently: 17 November 2026 versus 13 November 2026 for rybbit. That is 4 days apart.
Yes. This catalog marks both excelize and rybbit 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. rybbit is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
excelize scores 97.9 and rybbit scores 87.6. This page calls that a clear lead for excelize.