A · leads
activitywatch
94.2
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 12.6 · clear
A · leads
94.2
19,662 stars · MPL-2.0
B
81.6
21,239 stars · license n/a
activitywatch versus cube 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; cube is written mainly in Rust. The composite score is 94.2 for activitywatch and 81.6 for cube.
cube has 21,239 GitHub stars to activitywatch's 19,662, a gap of 1,577 (1.08×). Forks are 1,078 for activitywatch and 2,197 for cube. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 91 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and cube was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 1,189 for cube (0.056 per star). Issue-health scores are 84 and 52; 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. cube is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 78 for activitywatch and 30 for cube. This is a procurement signal, not legal advice.
Only activitywatch is marked self-hostable here (19,662 stars, deploy score 100). cube is not (21,239 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: activitywatch is open source, cube is unpriced in this catalog.
The lead is split. activitywatch is furthest ahead on self-hosting (100 to 35), while cube is furthest ahead on fork community (100 to 91). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 94.2 against cube at 81.6, a 12.6 point clear 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 | cube |
|---|---|---|
| GitHub stars | 19,662 | 21,239 |
| Forks | 1,078 | 2,197 |
| Open issues | 132 | 1,189 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 52 |
| License | 78 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 94.2 | 81.6 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
📊 Cube Core is open-source semantic layer for AI, BI and embedded analytics
cube has more GitHub stars: 21,239 versus 19,662 for activitywatch. The gap is 1,577 stars.
cube was pushed more recently: 17 November 2026 versus 15 November 2026 for activitywatch. That is 2 days apart.
Only activitywatch is marked self-hostable. cube is not.
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. cube is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 94.2 and cube scores 81.6. This page calls that a clear lead for activitywatch.