A · leads
excelize
97.2
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 5.7 · narrow
A · leads
97.2
21,136 stars · BSD-3-Clause
B
91.5
14,016 stars · Apache-2.0
excelize versus OpenSearch 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; OpenSearch is written mainly in Java. The composite score is 97.2 for excelize and 91.5 for OpenSearch.
excelize has 21,136 GitHub stars to OpenSearch's 14,016, a gap of 7,120 (1.51×). Forks are 2,004 for excelize and 3,088 for OpenSearch. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 95 versus 100.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and OpenSearch was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 3,385 for OpenSearch (0.242 per star). Issue-health scores are 84 and 34; 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. OpenSearch 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. License scores in this pair are 96 for excelize and 96 for OpenSearch. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and OpenSearch (14,016 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, OpenSearch is open source.
The lead is split. excelize is furthest ahead on issue health (84 to 34), while OpenSearch is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.2 against OpenSearch at 91.5, a 5.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 | OpenSearch |
|---|---|---|
| GitHub stars | 21,136 | 14,016 |
| Forks | 2,004 | 3,088 |
| Open issues | 176 | 3,385 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 84 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.2 | 91.5 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
🔎 Open source distributed and RESTful search engine.
excelize has more GitHub stars: 21,136 versus 14,016 for OpenSearch. The gap is 7,120 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and OpenSearch 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. OpenSearch 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
excelize scores 97.2 and OpenSearch scores 91.5. This page calls that a narrow lead for excelize.