A · leads
activitywatch
95.5
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 5.7 · narrow
A · leads
95.5
19,662 stars · MPL-2.0
B
89.8
10,214 stars · AGPL-3.0
activitywatch 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. activitywatch is written mainly in Python; ua-parser-js is written mainly in JavaScript. The composite score is 95.5 for activitywatch and 89.8 for ua-parser-js.
activitywatch has 19,662 GitHub stars to ua-parser-js's 10,214, a gap of 9,448 (1.93×). Forks are 1,078 for activitywatch 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 98 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and ua-parser-js was last pushed on 11 November 2026 (6 days ago). Open issues stand at 132 for activitywatch (0.007 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.
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. 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 78 for activitywatch and 52 for ua-parser-js. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 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: activitywatch is open source, ua-parser-js is open source.
The lead is split. activitywatch is furthest ahead on license flexibility (78 to 52), while ua-parser-js is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.5 against ua-parser-js at 89.8, 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 | activitywatch | ua-parser-js |
|---|---|---|
| GitHub stars | 19,662 | 10,214 |
| Forks | 1,078 | 1,219 |
| Open issues | 132 | 21 |
| Adoption | 100 | 93 |
| Activity | 100 | 92 |
| Community | 98 | 100 |
| Issue health | 84 | 96 |
| License | 78 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.5 | 89.8 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
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
activitywatch has more GitHub stars: 19,662 versus 10,214 for ua-parser-js. The gap is 9,448 stars.
activitywatch was pushed more recently: 15 November 2026 versus 11 November 2026 for ua-parser-js. That is 4 days apart.
Yes. This catalog marks both activitywatch and ua-parser-js 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. 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.
activitywatch scores 95.5 and ua-parser-js scores 89.8. This page calls that a narrow lead for activitywatch.