A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 1.6 · narrow
A · leads
95.8
19,662 stars · MPL-2.0
B
94.2
10,650 stars · MIT
activitywatch versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 95.8 for activitywatch and 94.2 for uPlot.
activitywatch has 19,662 GitHub stars to uPlot's 10,650, a gap of 9,012 (1.85×). Forks are 1,078 for activitywatch and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 88.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 132 for uPlot (0.012 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. uPlot 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 78 for activitywatch and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and uPlot (10,650 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, uPlot is open source.
The lead is split. activitywatch is furthest ahead on fork community (100 to 88), while uPlot is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.8 against uPlot at 94.2, a 1.6 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 | uPlot |
|---|---|---|
| GitHub stars | 19,662 | 10,650 |
| Forks | 1,078 | 472 |
| Open issues | 132 | 132 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 84 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 94.2 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
activitywatch has more GitHub stars: 19,662 versus 10,650 for uPlot. The gap is 9,012 stars.
uPlot 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 uPlot 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. uPlot 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.
activitywatch scores 95.8 and uPlot scores 94.2. This page calls that a narrow lead for activitywatch.