A · leads
excelize
94.8
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 6.2 · narrow
A · leads
94.8
21,136 stars · BSD-3-Clause
B
88.6
37,546 stars · license n/a
excelize versus langfuse 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; langfuse is written mainly in TypeScript. The composite score is 94.8 for excelize and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to excelize's 21,136, a gap of 16,410 (1.78×). Forks are 2,004 for excelize and 4,243 for langfuse. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 91 versus 100.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 84 and 70; 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. langfuse 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 langfuse. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and langfuse (37,546 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, langfuse is unpriced in this catalog.
The lead is split. excelize is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on fork community (100 to 91). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 94.8 against langfuse at 88.6, a 6.2 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 | langfuse |
|---|---|---|
| GitHub stars | 21,136 | 37,546 |
| Forks | 2,004 | 4,243 |
| Open issues | 176 | 1,173 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 94.8 | 88.6 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
langfuse has more GitHub stars: 37,546 versus 21,136 for excelize. The gap is 16,410 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and langfuse 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. langfuse 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 94.8 and langfuse scores 88.6. This page calls that a narrow lead for excelize.