A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 11.0 · clear
A · leads
97.9
21,136 stars · BSD-3-Clause
B
86.9
13,157 stars · license n/a
excelize versus openreplay 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; openreplay is written mainly in TypeScript. The composite score is 97.9 for excelize and 86.9 for openreplay.
excelize has 21,136 GitHub stars to openreplay's 13,157, a gap of 7,979 (1.61×). Forks are 2,004 for excelize and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 89.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 193 for openreplay (0.015 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. openreplay 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 openreplay. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and openreplay (13,157 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, openreplay is unpriced in this catalog.
excelize is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
excelize finishes ahead at 97.9 against openreplay at 86.9, a 11.0 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 | openreplay |
|---|---|---|
| GitHub stars | 21,136 | 13,157 |
| Forks | 2,004 | 891 |
| Open issues | 176 | 193 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 84 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 86.9 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
excelize has more GitHub stars: 21,136 versus 13,157 for openreplay. The gap is 7,979 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and openreplay 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. openreplay 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.9 and openreplay scores 86.9. This page calls that a clear lead for excelize.