A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 5.1 · narrow
A · leads
89.4
50,382 stars · AGPL-3.0
B
84.3
10,214 stars · AGPL-3.0
Metabase versus ua-parser-js is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; ua-parser-js is written mainly in JavaScript. The composite score is 89.4 for Metabase and 84.3 for ua-parser-js.
Metabase has 50,382 GitHub stars to ua-parser-js's 10,214, a gap of 40,168 (4.93×). Forks are 7,016 for Metabase and 1,219 for ua-parser-js. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 80.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and ua-parser-js was last pushed on 11 November 2026 (6 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 21 for ua-parser-js (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 92.
Both Metabase and ua-parser-js are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and ua-parser-js (10,214 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: Metabase is freemium, ua-parser-js is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 80), while ua-parser-js is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against ua-parser-js at 84.3, a 5.1 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 | Metabase | ua-parser-js |
|---|---|---|
| GitHub stars | 50,382 | 10,214 |
| Forks | 7,016 | 1,219 |
| Open issues | 4,696 | 21 |
| Adoption | 100 | 85 |
| Activity | 100 | 92 |
| Community | 100 | 80 |
| Issue health | 52 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 84.3 |
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
UAParser.js: The Essential Web Development Tool for User-Agent Detection. Detect Browsers, OS, Devices, Bots, Apps, AI Crawlers, and more. Run in Browser or Node
Metabase has more GitHub stars: 50,382 versus 10,214 for ua-parser-js. The gap is 40,168 stars.
Metabase was pushed more recently: 17 November 2026 versus 11 November 2026 for ua-parser-js. That is 6 days apart.
Yes. This catalog marks both Metabase and ua-parser-js as self-hostable. Confirm each project's deploy docs before you plan a migration.
Metabase 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. ua-parser-js 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.
Metabase scores 89.4 and ua-parser-js scores 84.3. This page calls that a narrow lead for Metabase.