Skip to content
gitdebt

plausible/analytics vs umami-software/umami

  • plausible/analytics

    Stars

    29,097

    First recorded star in 2019.

  • umami-software/umami

    Stars

    38,844

    First recorded star in 2020.

Star history overlay
31k STARS7 YRplausible/analytics24kumami-software/umami31k

plausible/analytics: 23,557 stars on September 16, 2026. umami-software/umami: 31,001 stars on September 16, 2026.

Star history for plausible/analytics
DateStars
September 2, 20191
November 10, 201994
January 19, 2020154
March 24, 2020194
April 27, 2020587
May 27, 2020883
June 25, 20201250
July 24, 20201649
August 23, 20202583
September 21, 20202926
October 26, 20204220
November 24, 20204500
December 23, 20204846
January 21, 20215259
February 19, 20215642
March 20, 20216637
April 18, 20217061
May 20, 20217423
June 18, 20217660
July 17, 20217917
August 15, 20218112
September 16, 20218402
October 16, 20218622
November 21, 20218859
December 20, 20219080
January 18, 20229480
February 16, 20229852
March 17, 202210147
April 15, 202210465
May 14, 202210770
June 18, 202211068
July 17, 202211428
August 15, 202211713
September 13, 202212093
October 12, 202212359
November 10, 202212618
December 9, 202212856
January 8, 202313125
February 6, 202313446
March 7, 202313780
April 5, 202314055
May 4, 202314297
June 2, 202314675
July 1, 202314967
July 30, 202315248
August 28, 202315552
September 26, 202315829
October 25, 202316186
November 23, 202316497
December 22, 202316786
January 26, 202417110
February 24, 202417408
March 24, 202417726
April 22, 202417997
May 21, 202418343
June 19, 202418626
July 18, 202418911
August 16, 202419213
September 14, 202419486
October 13, 202419807
November 11, 202420183
December 10, 202420597
January 8, 202520874
February 6, 202521166
March 7, 202521454
April 5, 202521750
May 4, 202522060
June 2, 202522286
July 3, 202522441
August 1, 202522580
September 5, 202522741
October 5, 202522850
November 11, 202522950
December 11, 202523037
January 12, 202623133
February 20, 202623203
March 29, 202623265
May 6, 202623310
June 12, 202623494
September 16, 202623557
Star history for umami-software/umami
DateStars
August 17, 20203
September 13, 20203191
October 9, 20203889
November 5, 20204513
December 1, 20204757
December 27, 20204944
January 24, 20215166
February 19, 20216000
March 18, 20216271
April 13, 20216419
May 18, 20217260
June 13, 20217769
July 9, 20217955
August 5, 20218167
September 3, 20218344
September 30, 20218589
November 5, 20218686
December 1, 20218871
December 28, 20219038
January 23, 20229267
February 18, 20229540
March 17, 20229880
April 12, 202210174
May 8, 202210706
June 4, 202211380
June 30, 202211646
July 27, 202211965
August 22, 202212301
September 17, 202212940
October 14, 202213164
November 14, 202213462
December 11, 202213691
January 6, 202313886
February 2, 202314187
February 28, 202314501
March 26, 202314802
April 22, 202315152
May 18, 202315516
June 13, 202315765
July 10, 202316003
August 5, 202316311
September 1, 202316582
September 27, 202316804
October 23, 202317073
November 19, 202317330
December 15, 202317603
January 10, 202417937
February 6, 202418299
March 3, 202418694
March 30, 202419102
April 30, 202419502
May 27, 202419855
June 22, 202420179
July 18, 202420508
August 14, 202420835
September 9, 202421732
October 6, 202422060
November 1, 202422389
November 27, 202422857
December 24, 202423228
January 19, 202523611
February 14, 202524120
March 13, 202525021
April 8, 202525455
May 5, 202525886
May 31, 202526236
June 26, 202526439
July 23, 202526701
August 18, 202528348
September 13, 202528652
October 21, 202528882
November 16, 202529907
December 13, 202530150
January 8, 202630395
February 4, 202630551
March 2, 202630691
April 1, 202630785
May 1, 202630871
June 3, 202630925
September 16, 202631001
add a third repository

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,097Best result in this row: 38,844
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+63Best result in this row: +69
ForksCurrent public GitHub metadata total.Not availableNot available
Largest package audienceLargest resolved registry total; sources are shown explicitly.No resolved packageNo resolved package
Repository ageElapsed years since the GitHub creation timestamp.7.8 years6.2 years

Codebase

Size and technical center of gravity

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

Maintenance

Commit volume and recent operating cadence

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

Ownership

How broadly maintenance responsibility is distributed

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

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.Not availableNot available
Recent TODO/FIXME movementLatest cumulative marker count and its change over the trailing 90 days.Not availableNot available

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 put them on one source: since July 2026 a stargazer-list series stops on a fixed date, while a series rebuilt from public archive events keeps receiving points. Each column below states its own reading.

How the star series for plausible/analytics and umami-software/umami were read
Fieldplausible/analyticsumami-software/umami
SourceHistorical star dataHistorical star data
CoverageCovers through September 16, 2026Covers through September 16, 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 38,844 stars for umami-software/umami and 29,097 for plausible/analytics.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. plausible/analytics — Historical star data · Covers through September 16, 2026 · Still updating. umami-software/umami — Historical star data · Covers through September 16, 2026 · Still updating. Since July 2026 GitHub serves a repository's stargazer list only to its own admins and collaborators, so one series can stop on a fixed date while the other keeps flowing from public archive events.

  • 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.