A
activitywatch
94.4
19,662 stars · MPL-2.0
Analytics
excelize leads by 3.5 · narrow
A
94.4
19,662 stars · MPL-2.0
B · leads
97.9
21,136 stars · BSD-3-Clause
activitywatch versus excelize is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. activitywatch is written mainly in Python; excelize is written mainly in Go. The composite score is 94.4 for activitywatch and 97.9 for excelize.
excelize has 21,136 GitHub stars to activitywatch's 19,662, a gap of 1,474 (1.07×). Forks are 1,078 for activitywatch and 2,004 for excelize. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 92 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and excelize was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 176 for excelize (0.008 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
activitywatch is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 78 for activitywatch and 96 for excelize. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 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: activitywatch is open source, excelize is open source.
excelize is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 18 points (78 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
excelize finishes ahead at 97.9 against activitywatch at 94.4, a 3.5 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 | activitywatch | excelize |
|---|---|---|
| GitHub stars | 19,662 | 21,136 |
| Forks | 1,078 | 2,004 |
| Open issues | 132 | 176 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 84 | 84 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.4 | 97.9 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
excelize has more GitHub stars: 21,136 versus 19,662 for activitywatch. The gap is 1,474 stars.
excelize was pushed more recently: 17 November 2026 versus 15 November 2026 for activitywatch. That is 2 days apart.
Yes. This catalog marks both activitywatch and excelize as self-hostable. Confirm each project's deploy docs before you plan a migration.
activitywatch is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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.9 and activitywatch scores 94.4. This page calls that a narrow lead for excelize.