A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 4.7 · narrow
A · leads
97.9
21,136 stars · BSD-3-Clause
B
93.2
13,817 stars · MIT
excelize versus partytown 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; partytown is written mainly in TypeScript. The composite score is 97.9 for excelize and 93.2 for partytown.
excelize has 21,136 GitHub stars to partytown's 13,817, a gap of 7,319 (1.53×). Forks are 2,004 for excelize and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 81.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 176 for excelize (0.008 per star) and 1 for partytown (0.000 per star). Issue-health scores are 84 and 96; 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. partytown 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 partytown. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and partytown (13,817 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, partytown is open source.
The lead is split. excelize is furthest ahead on fork community (100 to 81), while partytown is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.9 against partytown at 93.2, a 4.7 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 | partytown |
|---|---|---|
| GitHub stars | 21,136 | 13,817 |
| Forks | 2,004 | 460 |
| Open issues | 176 | 1 |
| Adoption | 100 | 96 |
| Activity | 100 | 92 |
| Community | 100 | 81 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.2 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
excelize has more GitHub stars: 21,136 versus 13,817 for partytown. The gap is 7,319 stars.
excelize was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.
Yes. This catalog marks both excelize and partytown 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. partytown 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 partytown scores 93.2. This page calls that a narrow lead for excelize.