Skip to content

plausible/analytics vs umami-software/umami

  • plausible/analytics

    Stars

    29,844

    First recorded star in 2019.

  • umami-software/umami

    Stars

    40,137

    First recorded star in 2020.

Star history overlay

40k STARS7 YR 6 MOplausible/analytics30kumami-software/umami40k

plausible/analytics: 29,844 stars on November 13, 2026. umami-software/umami: 40,137 stars on November 14, 2026.

Star history for plausible/analytics
DateStars
May 20, 20191
November 20, 201994
February 25, 2020151
April 13, 2020430
May 16, 2020684
June 16, 2020922
July 17, 20201398
August 18, 20202262
September 18, 20202625
October 19, 20203710
November 26, 20204081
December 27, 20204423
January 27, 20214822
February 28, 20215252
March 31, 20216595
May 1, 20216982
June 1, 20217320
July 3, 20217548
August 3, 20217782
September 3, 20218018
October 5, 20218312
November 5, 20218592
December 6, 20218846
January 6, 20229121
February 7, 20229548
March 10, 20229870
April 10, 202210211
May 12, 202210532
June 12, 202210789
July 13, 202211217
August 20, 202211601
September 20, 202211916
October 21, 202212207
November 22, 202212490
December 23, 202212686
January 23, 202312997
February 23, 202313349
March 27, 202313685
April 27, 202313959
May 28, 202314337
June 29, 202314653
July 30, 202314949
August 30, 202315279
October 1, 202315581
November 1, 202315980
December 2, 202316268
January 2, 202416588
February 3, 202416923
March 5, 202417232
April 5, 202417566
May 13, 202418004
June 13, 202418284
July 14, 202418594
August 15, 202418923
September 15, 202419210
October 16, 202419583
November 17, 202419986
December 18, 202420406
January 18, 202520713
February 18, 202521044
March 22, 202521381
April 22, 202521749
May 23, 202522060
June 24, 202522337
July 25, 202522581
August 25, 202522817
September 25, 202523039
October 27, 202523295
November 27, 202523486
December 28, 202523708
February 4, 202623908
March 7, 202624117
April 7, 202624343
May 9, 202624624
June 9, 202626812
July 10, 202627505
August 11, 202628346
September 11, 202628944
October 12, 202629334
November 13, 202629844
Star history for umami-software/umami
DateStars
August 17, 202031
September 14, 20203275
October 13, 20204045
November 10, 20204489
December 9, 20204709
January 6, 20214878
February 4, 20215646
March 4, 20215893
April 2, 20216089
May 1, 20216222
June 5, 20217347
July 3, 20217573
August 1, 20217772
August 29, 20217945
September 27, 20218174
October 25, 20218353
November 24, 20218538
December 23, 20218693
January 21, 20228920
February 18, 20229190
March 19, 20229525
April 16, 20229837
May 15, 202210499
June 12, 202211064
July 11, 202211368
August 9, 202211681
September 6, 202212050
October 5, 202212651
November 2, 202212895
December 1, 202213173
January 4, 202313416
February 1, 202313736
March 2, 202314078
March 31, 202314402
April 28, 202314816
May 27, 202315205
June 24, 202315423
July 23, 202315701
August 20, 202316022
September 18, 202316306
October 16, 202316525
November 14, 202316822
December 12, 202317117
January 10, 202417487
February 7, 202417853
March 7, 202418301
April 4, 202418729
May 3, 202419086
June 1, 202419445
June 29, 202419799
August 2, 202420215
August 31, 202421112
September 28, 202421509
October 27, 202421868
November 24, 202422381
December 23, 202422797
January 21, 202523232
February 18, 202524175
March 19, 202524880
April 16, 202525377
May 15, 202525848
June 12, 202526245
July 11, 202526685
August 8, 202527152
September 6, 202530025
October 4, 202530422
November 2, 202530845
November 30, 202533291
December 29, 202533922
January 26, 202634403
March 2, 202635011
March 30, 202635496
April 28, 202636015
May 26, 202636526
June 24, 202637014
July 22, 202637574
August 20, 202638096
September 17, 202638752
October 16, 202639340
November 14, 202640137

Repository health compared

Live analysis · unavailable data stays labelled

Popularity is only one axis. Compare technical scale, maintenance cadence, ownership resilience and change pressure against the same completed analysis that sits behind each report.

Reach

Popularity and real-world adoption

Signalplausible/analyticsumami-software/umami
GitHub starsCurrent public GitHub metadata total.29,844Best result in this row: 40,137
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+1,498Best result in this row: +2,153
ForksCurrent public GitHub metadata total.Reading…Reading…
Largest package audienceLargest resolved registry total; sources are shown explicitly.Reading…Reading…
Repository ageElapsed years since the GitHub creation timestamp.7.9 years6.3 years

Codebase

Size and technical center of gravity

Signalplausible/analyticsumami-software/umami
Dominant languageLargest share of analyzed code lines at current HEAD.Reading…Reading…
Code linesAnalyzed source lines at current HEAD, excluding blanks and comments.Reading…Reading…
Languages representedLanguages with non-zero files or line counts.Reading…Reading…

Maintenance

Commit volume and recent operating cadence

Signalplausible/analyticsumami-software/umami
Repository commitsFull repository commit total reported by the analysis.Reading…Reading…
Commits · trailing 90dCommit count in the newest 90 days covered by the repository analysis.Reading…Reading…

Ownership

How broadly maintenance responsibility is distributed

Signalplausible/analyticsumami-software/umami
Bus factorFewest analyzed contributors carrying at least half the commits.Reading…Reading…
Top contributor concentrationShare of attributed commits carried by the most active contributor.Reading…Reading…

Change signals

Debt markers and fix pressure in frequently changed files

Signalplausible/analyticsumami-software/umami
Fix-labelled share · frequently changed filesFix-labelled commits divided by commits across the analyzed high-frequency file set.Reading…Reading…
Recent TODO/FIXME movementLatest cumulative marker count and its change over the trailing 90 days.Reading…Reading…

Both curves are drawn on shared axes. They are not drawn from a shared source: each series names its own below.

One axis, two sources

The overlay puts both repositories on one axis. It does not always put them on one source: a series not yet read again from GitHub's star history can stop on the date GitHub closed its stargazer list, or be rebuilt from public archive events. Each column below states its own reading.

How the star series for plausible/analytics and umami-software/umami were read
Fieldplausible/analyticsumami-software/umami
SourceGitHub star historyGitHub star history
CoverageCovers through November 14, 2026Covers through November 14, 2026
StateStill updatingStill updating

No row states how much of a history is missing. An archive series records star actions and not unstars, so it can exceed a repository's own star total, and a figure for the difference would be wrong exactly where it looks most precise.

Notes on this comparison

  • Which has more GitHub stars, plausible/analytics or umami-software/umami?

    GitHub reports 40,137 stars for umami-software/umami and 29,844 for plausible/analytics.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. plausible/analytics — GitHub star history · Covers through November 14, 2026 · Still updating. umami-software/umami — GitHub star history · Covers through November 14, 2026 · Still updating. A series read from GitHub's star history runs to its latest read. One read before that existed can stop on the date GitHub closed its stargazer list in July 2026, or come from public archive events, until gitdebt reads it again.

  • How is this comparison computed?

    Star totals come from public repository metadata. The two curves are each repository's stored star series drawn on shared axes, from whichever source is named above. Repository-health figures are computed independently from each project's commit history.