A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 2.8 · narrow
A · leads
88.6
37,546 stars · license n/a
B
85.8
10,214 stars · AGPL-3.0
langfuse 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. langfuse is written mainly in TypeScript; ua-parser-js is written mainly in JavaScript. The composite score is 88.6 for langfuse and 85.8 for ua-parser-js.
langfuse has 37,546 GitHub stars to ua-parser-js's 10,214, a gap of 27,332 (3.68×). Forks are 4,243 for langfuse and 1,219 for ua-parser-js. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 85.
Push history: langfuse 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 1,173 for langfuse (0.031 per star) and 21 for ua-parser-js (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 92.
langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for langfuse and 52 for ua-parser-js. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 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: langfuse is unpriced in this catalog, ua-parser-js is open source.
The lead is split. langfuse is furthest ahead on fork community (100 to 85), while ua-parser-js is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against ua-parser-js at 85.8, a 2.8 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 | langfuse | ua-parser-js |
|---|---|---|
| GitHub stars | 37,546 | 10,214 |
| Forks | 4,243 | 1,219 |
| Open issues | 1,173 | 21 |
| Adoption | 100 | 88 |
| Activity | 100 | 92 |
| Community | 100 | 85 |
| Issue health | 70 | 96 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 85.8 |
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
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
langfuse has more GitHub stars: 37,546 versus 10,214 for ua-parser-js. The gap is 27,332 stars.
langfuse 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 langfuse and ua-parser-js as self-hostable. Confirm each project's deploy docs before you plan a migration.
langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
langfuse scores 88.6 and ua-parser-js scores 85.8. This page calls that a narrow lead for langfuse.