A · leads
activitywatch
94.5
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 2.3 · narrow
A · leads
94.5
19,662 stars · MPL-2.0
B
92.2
9,556 stars · Apache-2.0
activitywatch versus amplify-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; amplify-js is written mainly in TypeScript. The composite score is 94.5 for activitywatch and 92.2 for amplify-js.
activitywatch has 19,662 GitHub stars to amplify-js's 9,556, a gap of 10,106 (2.06×). Forks are 1,078 for activitywatch and 2,171 for amplify-js. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 91 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and amplify-js was last pushed on 16 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 518 for amplify-js (0.054 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. amplify-js is listed as Apache-2.0, 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 amplify-js. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and amplify-js (9,556 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, amplify-js is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 52), while amplify-js is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 94.5 against amplify-js at 92.2, a 2.3 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 | amplify-js |
|---|---|---|
| GitHub stars | 19,662 | 9,556 |
| Forks | 1,078 | 2,171 |
| Open issues | 132 | 518 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 52 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.5 | 92.2 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
A declarative JavaScript library for application development using cloud services.
activitywatch has more GitHub stars: 19,662 versus 9,556 for amplify-js. The gap is 10,106 stars.
amplify-js was pushed more recently: 16 November 2026 versus 15 November 2026 for activitywatch. That is 2 days apart.
Yes. This catalog marks both activitywatch and amplify-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. amplify-js is listed as Apache-2.0, 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 94.5 and amplify-js scores 92.2. This page calls that a narrow lead for activitywatch.