A · leads
lago
93.0
10,891 stars · AGPL-3.0
Analytics
lago leads by 1.2 · narrow
A · leads
93.0
10,891 stars · AGPL-3.0
B
91.8
10,214 stars · AGPL-3.0
lago 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. lago is written mainly in Go; ua-parser-js is written mainly in JavaScript. The composite score is 93.0 for lago and 91.8 for ua-parser-js.
lago has 10,891 GitHub stars to ua-parser-js's 10,214, a gap of 677 (1.07×). Forks are 798 for lago and 1,219 for ua-parser-js. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 94 versus 100.
Push history: lago 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 17 for lago (0.002 per star) and 21 for ua-parser-js (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
Both lago 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 lago (10,891 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: lago is open source, ua-parser-js is open source.
The lead is split. lago is furthest ahead on recent activity (100 to 92), while ua-parser-js is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
lago finishes ahead at 93.0 against ua-parser-js at 91.8, a 1.2 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 | lago | ua-parser-js |
|---|---|---|
| GitHub stars | 10,891 | 10,214 |
| Forks | 798 | 1,219 |
| Open issues | 17 | 21 |
| Adoption | 100 | 99 |
| Activity | 100 | 92 |
| Community | 94 | 100 |
| Issue health | 96 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.0 | 91.8 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
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
lago has more GitHub stars: 10,891 versus 10,214 for ua-parser-js. The gap is 677 stars.
lago 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 lago and ua-parser-js as self-hostable. Confirm each project's deploy docs before you plan a migration.
lago 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.
lago scores 93.0 and ua-parser-js scores 91.8. This page calls that a narrow lead for lago.