A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 6.9 · narrow
A · leads
95.8
19,662 stars · MPL-2.0
B
88.9
13,328 stars · AGPL-3.0
activitywatch versus rybbit 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; rybbit is written mainly in TypeScript. The composite score is 95.8 for activitywatch and 88.9 for rybbit.
activitywatch has 19,662 GitHub stars to rybbit's 13,328, a gap of 6,334 (1.48×). Forks are 1,078 for activitywatch and 791 for rybbit. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 96.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and rybbit was last pushed on 13 November 2026 (4 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 212 for rybbit (0.016 per star). Issue-health scores are 84 and 84; 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. rybbit 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 rybbit. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and rybbit (13,328 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, rybbit is open source.
activitywatch is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is license flexibility at 26 points (78 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
activitywatch finishes ahead at 95.8 against rybbit at 88.9, a 6.9 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 | rybbit |
|---|---|---|
| GitHub stars | 19,662 | 13,328 |
| Forks | 1,078 | 791 |
| Open issues | 132 | 212 |
| Adoption | 100 | 96 |
| Activity | 100 | 92 |
| Community | 100 | 96 |
| Issue health | 84 | 84 |
| License | 78 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 88.9 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
activitywatch has more GitHub stars: 19,662 versus 13,328 for rybbit. The gap is 6,334 stars.
activitywatch was pushed more recently: 15 November 2026 versus 13 November 2026 for rybbit. That is 2 days apart.
Yes. This catalog marks both activitywatch and rybbit 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. rybbit 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.8 and rybbit scores 88.9. This page calls that a narrow lead for activitywatch.