A
amplify-js
92.0
9,556 stars · Apache-2.0
Analytics
excelize leads by 5.8 · narrow
A
92.0
9,556 stars · Apache-2.0
B · leads
97.8
21,136 stars · BSD-3-Clause
amplify-js versus excelize is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. amplify-js is written mainly in TypeScript; excelize is written mainly in Go. The composite score is 92.0 for amplify-js and 97.8 for excelize.
excelize has 21,136 GitHub stars to amplify-js's 9,556, a gap of 11,580 (2.21×). Forks are 2,171 for amplify-js and 2,004 for excelize. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 100 versus 99.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and excelize was last pushed on 17 November 2026 (0 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 176 for excelize (0.008 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
amplify-js is listed as Apache-2.0, 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. 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. License scores in this pair are 96 for amplify-js and 96 for excelize. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 stars) and excelize (21,136 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: amplify-js is open source, excelize is open source.
The lead is split. amplify-js is furthest ahead on fork community (100 to 99), while excelize is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.8 against amplify-js at 92.0, a 5.8 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 | amplify-js | excelize |
|---|---|---|
| GitHub stars | 9,556 | 21,136 |
| Forks | 2,171 | 2,004 |
| Open issues | 518 | 176 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.0 | 97.8 |
A declarative JavaScript library for application development using cloud services.
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
excelize has more GitHub stars: 21,136 versus 9,556 for amplify-js. The gap is 11,580 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both amplify-js and excelize as self-hostable. Confirm each project's deploy docs before you plan a migration.
amplify-js is listed as Apache-2.0, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
excelize scores 97.8 and amplify-js scores 92.0. This page calls that a narrow lead for excelize.