A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 9.2 · clear
A · leads
97.9
21,136 stars · BSD-3-Clause
B
88.7
10,214 stars · AGPL-3.0
excelize versus ua-parser-js 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; ua-parser-js is written mainly in JavaScript. The composite score is 97.9 for excelize and 88.7 for ua-parser-js.
excelize has 21,136 GitHub stars to ua-parser-js's 10,214, a gap of 10,922 (2.07×). Forks are 2,004 for excelize and 1,219 for ua-parser-js. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 94.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and ua-parser-js was last pushed on 11 November 2026 (6 days ago). Open issues stand at 176 for excelize (0.008 per star) and 21 for ua-parser-js (0.002 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. ua-parser-js 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 ua-parser-js. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and ua-parser-js (10,214 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, ua-parser-js is open source.
The lead is split. excelize is furthest ahead on license flexibility (96 to 52), while ua-parser-js is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.9 against ua-parser-js at 88.7, a 9.2 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 | ua-parser-js |
|---|---|---|
| GitHub stars | 21,136 | 10,214 |
| Forks | 2,004 | 1,219 |
| Open issues | 176 | 21 |
| Adoption | 100 | 93 |
| Activity | 100 | 92 |
| Community | 100 | 94 |
| Issue health | 84 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.7 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
UAParser.js: The Essential Web Development Tool for User-Agent Detection. Detect Browsers, OS, Devices, Bots, Apps, AI Crawlers, and more. Run in Browser or Node
excelize has more GitHub stars: 21,136 versus 10,214 for ua-parser-js. The gap is 10,922 stars.
excelize was pushed more recently: 17 November 2026 versus 11 November 2026 for ua-parser-js. That is 6 days apart.
Yes. This catalog marks both excelize and ua-parser-js 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. ua-parser-js 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 ua-parser-js scores 88.7. This page calls that a clear lead for excelize.