Skip to content

microsoft/terminal vs wez/wezterm

  • microsoft/terminal

    Stars

    104,903

    First recorded star in 2017.

  • wez/wezterm

    Stars

    28,916

    First recorded star in 2018.

Star history overlay

115k STARS9 YR 1 MOmicrosoft/terminal115kwez/wezterm23k

microsoft/terminal: 114,741 stars on September 16, 2026. wez/wezterm: 23,266 stars on September 16, 2026.

Star history for microsoft/terminal
DateStars
August 12, 201740
October 6, 2017162
November 24, 2017274
January 10, 2018363
March 3, 2018443
April 24, 2018534
June 6, 2018650
July 23, 2018753
September 6, 2018874
October 23, 2018990
December 17, 20181148
January 25, 20191317
March 7, 20191475
April 15, 20191661
May 25, 201941513
July 3, 201949314
August 11, 201951899
September 19, 201953853
October 28, 201955759
December 6, 201957609
January 14, 202059287
February 22, 202061040
April 1, 202062886
May 10, 202064979
June 18, 202068981
July 27, 202070889
September 5, 202072315
October 14, 202073508
November 22, 202074859
December 31, 202076101
February 16, 202177843
March 27, 202178971
May 5, 202180159
June 16, 202181619
July 25, 202182980
September 4, 202184183
October 14, 202185065
November 27, 202185942
January 5, 202287076
February 13, 202288721
March 25, 202289966
May 3, 202291043
June 11, 202292073
July 20, 202292744
August 28, 202293847
October 6, 202294590
November 14, 202295320
December 23, 202296126
January 31, 202396915
March 11, 202397643
April 27, 202398465
June 5, 202399171
July 14, 202399859
August 22, 2023100499
September 30, 2023101366
November 8, 2023102071
December 17, 2023102784
January 25, 2024103363
March 4, 2024104388
April 12, 2024105011
May 21, 2024105676
June 29, 2024106265
August 7, 2024106855
September 15, 2024107471
October 24, 2024108197
December 2, 2024108893
January 10, 2025109537
February 18, 2025110410
March 29, 2025111054
May 7, 2025111700
June 23, 2025112288
August 1, 2025112593
September 9, 2025113254
October 24, 2025113687
December 2, 2025113877
January 10, 2026114102
February 18, 2026114327
March 31, 2026114504
May 13, 2026114657
September 16, 2026114741
Star history for wez/wezterm
DateStars
February 8, 20181
April 10, 201934
October 9, 201974
December 22, 2019128
February 24, 2020173
April 20, 2020220
June 24, 2020358
August 26, 2020404
October 16, 2020462
November 21, 2020534
January 3, 2021642
February 2, 2021701
March 8, 2021770
April 9, 20211521
May 7, 20211784
June 10, 20211895
July 14, 20211997
August 13, 20212135
September 14, 20212297
October 16, 20212424
November 22, 20212537
December 20, 20212904
January 17, 20223143
February 14, 20223315
March 14, 20223588
April 11, 20224019
May 9, 20224334
June 6, 20224522
July 4, 20224886
August 1, 20225240
September 3, 20225658
October 1, 20225920
October 29, 20226183
November 26, 20226480
December 24, 20226693
January 21, 20237002
February 18, 20237424
March 18, 20237768
April 15, 20238259
May 13, 20238637
June 11, 20239046
July 9, 20239414
August 6, 20239809
September 3, 202310133
October 1, 202310497
October 29, 202310835
November 26, 202311258
December 24, 202311650
January 21, 202412164
February 18, 202412635
March 22, 202413323
April 19, 202413749
May 17, 202414183
June 14, 202414784
July 12, 202415147
August 9, 202415698
September 6, 202416758
October 4, 202417249
November 1, 202417831
November 29, 202418322
December 28, 202418812
January 25, 202519280
February 22, 202519636
March 22, 202520010
April 19, 202520315
May 17, 202520738
June 14, 202520959
July 12, 202521187
August 9, 202521423
September 6, 202521619
October 15, 202521903
November 12, 202522066
December 11, 202522218
January 8, 202622433
February 5, 202622664
March 5, 202622892
April 3, 202623038
May 3, 202623144
June 7, 202623205
September 16, 202623266

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

Signalmicrosoft/terminalwez/wezterm
GitHub starsCurrent public GitHub metadata total.Best result in this row: 104,90328,916
Stars gained · trailing 90dChange in the newest 90 days covered by each cached series.+51Best result in this row: +61
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.9.1 years8.6 years

Codebase

Size and technical center of gravity

Signalmicrosoft/terminalwez/wezterm
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

Signalmicrosoft/terminalwez/wezterm
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

Signalmicrosoft/terminalwez/wezterm
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

Signalmicrosoft/terminalwez/wezterm
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 microsoft/terminal and wez/wezterm were read
Fieldmicrosoft/terminalwez/wezterm
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, microsoft/terminal or wez/wezterm?

    GitHub reports 104,903 stars for microsoft/terminal and 28,916 for wez/wezterm.

  • Do both star histories cover the same period?

    Not necessarily, and each chart names its own. microsoft/terminal — Historical star data · Covers through September 16, 2026 · Still updating. wez/wezterm — 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.