A · leads
amplify-js
94.2
9,556 stars · Apache-2.0
Analytics
amplify-js leads by 14.4 · clear
A · leads
94.2
9,556 stars · Apache-2.0
B
79.8
11,031 stars · MIT
amplify-js versus dashboards is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. amplify-js is written mainly in TypeScript; dashboards is written mainly in HTML. The composite score is 94.2 for amplify-js and 79.8 for dashboards.
dashboards has 11,031 GitHub stars to amplify-js's 9,556, a gap of 1,475 (1.15×). Forks are 2,171 for amplify-js and 1,386 for dashboards. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 94.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and dashboards was last pushed on 02 November 2021 (1841 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 6 for dashboards (0.001 per star). Issue-health scores are 52 and 96; activity scores are 100 and 16.
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. dashboards 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 96 for amplify-js and 96 for dashboards. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 stars) and dashboards (11,031 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, dashboards is open source.
The lead is split. amplify-js is furthest ahead on recent activity (100 to 16), while dashboards is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
amplify-js finishes ahead at 94.2 against dashboards at 79.8, a 14.4 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 | amplify-js | dashboards |
|---|---|---|
| GitHub stars | 9,556 | 11,031 |
| Forks | 2,171 | 1,386 |
| Open issues | 518 | 6 |
| Adoption | 98 | 100 |
| Activity | 100 | 16 |
| Community | 100 | 94 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.2 | 79.8 |
A declarative JavaScript library for application development using cloud services.
Responsive dashboard templates 📊✨
dashboards has more GitHub stars: 11,031 versus 9,556 for amplify-js. The gap is 1,475 stars.
amplify-js was pushed more recently: 16 November 2026 versus 02 November 2021 for dashboards. That is 1841 days apart.
Yes. This catalog marks both amplify-js and dashboards 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. dashboards 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.
amplify-js scores 94.2 and dashboards scores 79.8. This page calls that a clear lead for amplify-js.