Skip to content
DevUtils Online

Analytics

player vs Umami

Umami leads by 18.0 · decisive

A

player

81.1

3,734 stars · MIT

B · leads

Umami

99.1

40,194 stars · MIT

player versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 81.1 for player and 99.1 for Umami.

Umami has 40,194 GitHub stars to player's 3,734, a gap of 36,460 (10.76×). Forks are 231 for player and 8,567 for Umami. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 60 versus 100.

Push history: player was last pushed on 07 October 2026 (40 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1 for player (0.000 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 78 and 100.

Both player and Umami are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Analytics, both player (3,734 stars) and Umami (40,194 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: player is open source, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 40 points (60 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

Umami finishes ahead at 99.1 against player at 81.1, a 18.0 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

player versus Umami metrics
Signal player Umami
GitHub stars 3,734 40,194
Forks 231 8,567
Open issues 1 136
Adoption 78 100
Activity 78 100
Community 60 100
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 81.1 99.1

player

Deprecated in favour of Video.js 10; security fixes only until January 2028. UI components and hooks for building video and audio players on the web.

Project site · GitHub · Full profile

Umami

Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, player or Umami?

Umami has more GitHub stars: 40,194 versus 3,734 for player. The gap is 36,460 stars.

Which was updated more recently, player or Umami?

Umami was pushed more recently: 17 November 2026 versus 07 October 2026 for player. That is 40 days apart.

Can I self-host both player and Umami?

Yes. This catalog marks both player and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, player or Umami?

player 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. Umami 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.

Who wins the player vs Umami score?

Umami scores 99.1 and player scores 81.1. This page calls that a decisive lead for Umami.

Related comparisons