A · leads
perspective
99.1
11,436 stars · Apache-2.0
Analytics
perspective leads by 3.5 · narrow
A · leads
99.1
11,436 stars · Apache-2.0
B
95.6
10,650 stars · MIT
perspective versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. perspective is written mainly in Rust; uPlot is written mainly in JavaScript. The composite score is 99.1 for perspective and 95.6 for uPlot.
perspective has 11,436 GitHub stars to uPlot's 10,650, a gap of 786 (1.07×). Forks are 1,358 for perspective and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 85.
Push history: perspective was last pushed on 16 November 2026 (1 day ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 29 for perspective (0.003 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
perspective 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 perspective and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both perspective (11,436 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: perspective is open source, uPlot is open source.
perspective is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 15 points (100 vs 85), and the tightest is self-hosting at 0 points (100 vs 100).
perspective finishes ahead at 99.1 against uPlot at 95.6, a 3.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 | perspective | uPlot |
|---|---|---|
| GitHub stars | 11,436 | 10,650 |
| Forks | 1,358 | 472 |
| Open issues | 29 | 132 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 95.6 |
A data visualization and analytics component, especially well-suited for large and/or streaming datasets.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
perspective has more GitHub stars: 11,436 versus 10,650 for uPlot. The gap is 786 stars.
uPlot was pushed more recently: 17 November 2026 versus 16 November 2026 for perspective. That is 1 days apart.
Yes. This catalog marks both perspective and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
perspective 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.
perspective scores 99.1 and uPlot scores 95.6. This page calls that a narrow lead for perspective.