A · level
amplify-js
94.3
9,556 stars · Apache-2.0
Analytics
Too close to call · 94.3 to 95.1
A · level
94.3
9,556 stars · Apache-2.0
B · level
95.1
10,650 stars · MIT
amplify-js versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 94.3 for amplify-js and 95.1 for uPlot.
uPlot has 10,650 GitHub stars to amplify-js's 9,556, a gap of 1,094 (1.11×). Forks are 2,171 for amplify-js and 472 for uPlot. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 80.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
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. uPlot 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 uPlot. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 stars) and uPlot (10,650 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, uPlot is open source.
The lead is split. amplify-js is furthest ahead on fork community (100 to 80), while uPlot is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: amplify-js 94.3, uPlot 95.1. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | uPlot |
|---|---|---|
| GitHub stars | 9,556 | 10,650 |
| Forks | 2,171 | 472 |
| Open issues | 518 | 132 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.3 | 95.1 |
A declarative JavaScript library for application development using cloud services.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
uPlot has more GitHub stars: 10,650 versus 9,556 for amplify-js. The gap is 1,094 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both amplify-js and uPlot 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. uPlot 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.
Neither tool clears a one-point margin. amplify-js scores 94.3 and uPlot scores 95.1.