A · leads
amplify-js
93.5
9,556 stars · Apache-2.0
Analytics
amplify-js leads by 4.5 · narrow
A · leads
93.5
9,556 stars · Apache-2.0
B
89.0
13,328 stars · AGPL-3.0
amplify-js versus rybbit is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 93.5 for amplify-js and 89.0 for rybbit.
rybbit has 13,328 GitHub stars to amplify-js's 9,556, a gap of 3,772 (1.39×). Forks are 2,171 for amplify-js and 791 for rybbit. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 87.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and rybbit was last pushed on 13 November 2026 (4 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 212 for rybbit (0.016 per star). Issue-health scores are 52 and 84; activity scores are 100 and 92.
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. 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 96 for amplify-js and 52 for rybbit. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 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: amplify-js is open source, rybbit is open source.
The lead is split. amplify-js is furthest ahead on license flexibility (96 to 52), while rybbit is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
amplify-js finishes ahead at 93.5 against rybbit at 89.0, a 4.5 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 | amplify-js | rybbit |
|---|---|---|
| GitHub stars | 9,556 | 13,328 |
| Forks | 2,171 | 791 |
| Open issues | 518 | 212 |
| Adoption | 96 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 87 |
| Issue health | 52 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.5 | 89.0 |
A declarative JavaScript library for application development using cloud services.
🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
rybbit has more GitHub stars: 13,328 versus 9,556 for amplify-js. The gap is 3,772 stars.
amplify-js was pushed more recently: 16 November 2026 versus 13 November 2026 for rybbit. That is 4 days apart.
Yes. This catalog marks both amplify-js and rybbit as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
amplify-js scores 93.5 and rybbit scores 89.0. This page calls that a narrow lead for amplify-js.