A
openreplay
89.4
13,157 stars · license n/a
Analytics
ua-parser-js leads by 1.8 · narrow
A
89.4
13,157 stars · license n/a
B · leads
91.2
10,214 stars · AGPL-3.0
openreplay 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. openreplay is written mainly in TypeScript; ua-parser-js is written mainly in JavaScript. The composite score is 89.4 for openreplay and 91.2 for ua-parser-js.
openreplay has 13,157 GitHub stars to ua-parser-js's 10,214, a gap of 2,943 (1.29×). Forks are 891 for openreplay and 1,219 for ua-parser-js. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 96 versus 100.
Push history: openreplay 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 193 for openreplay (0.015 per star) and 21 for ua-parser-js (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
openreplay 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 openreplay and 52 for ua-parser-js. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 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: openreplay is unpriced in this catalog, ua-parser-js is open source.
The lead is split. openreplay is furthest ahead on recent activity (100 to 92), while ua-parser-js is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.
ua-parser-js finishes ahead at 91.2 against openreplay at 89.4, a 1.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 | openreplay | ua-parser-js |
|---|---|---|
| GitHub stars | 13,157 | 10,214 |
| Forks | 891 | 1,219 |
| Open issues | 193 | 21 |
| Adoption | 100 | 97 |
| Activity | 100 | 92 |
| Community | 96 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 91.2 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
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
openreplay has more GitHub stars: 13,157 versus 10,214 for ua-parser-js. The gap is 2,943 stars.
openreplay 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 openreplay and ua-parser-js as self-hostable. Confirm each project's deploy docs before you plan a migration.
openreplay 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.
ua-parser-js scores 91.2 and openreplay scores 89.4. This page calls that a narrow lead for ua-parser-js.