A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 1.4 · narrow
A · leads
95.8
19,662 stars · MPL-2.0
B
94.4
13,817 stars · MIT
activitywatch versus partytown 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; partytown is written mainly in TypeScript. The composite score is 95.8 for activitywatch and 94.4 for partytown.
activitywatch has 19,662 GitHub stars to partytown's 13,817, a gap of 5,845 (1.42×). Forks are 1,078 for activitywatch and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 88.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 1 for partytown (0.000 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. partytown 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 partytown. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and partytown (13,817 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, partytown is open source.
The lead is split. activitywatch is furthest ahead on fork community (100 to 88), while partytown is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.8 against partytown at 94.4, a 1.4 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 | partytown |
|---|---|---|
| GitHub stars | 19,662 | 13,817 |
| Forks | 1,078 | 460 |
| Open issues | 132 | 1 |
| Adoption | 100 | 96 |
| Activity | 100 | 92 |
| Community | 100 | 88 |
| Issue health | 84 | 96 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 94.4 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
activitywatch has more GitHub stars: 19,662 versus 13,817 for partytown. The gap is 5,845 stars.
activitywatch was pushed more recently: 15 November 2026 versus 09 November 2026 for partytown. That is 5 days apart.
Yes. This catalog marks both activitywatch and partytown 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. partytown 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 partytown scores 94.4. This page calls that a narrow lead for activitywatch.