Problem
gh repo view --json repositoryTopics returns exactly 20 topics - GitHub's hard maximum - so discovery tags can no longer be added, only swapped, and the current set spends slots on overlaps while omitting the ecosystem tags a developer browses by. Present: csharp, gaming, network-monitor, performance, process-manager, system-monitor, system-utility, uninstaller, windows, windows-11, winget, debloat, disk-cleanup, pc-optimizer, privacy-tools, task-manager-alternative, windows-privacy, ccleaner-alternative, system-cleaner, windows-tweaks. Three pairs are effectively the same query surface: disk-cleanup/system-cleaner, pc-optimizer/windows-tweaks, privacy-tools/windows-privacy. Missing entirely: wpf and dotnet - the two tags through which .NET desktop developers browse GitHub, and the audience most likely to star a portfolio piece - plus windows-10, even though README.md:32 and the Platform badge both promise Windows 10 support.
Proposed solution
Swap, don't append (the cap is already reached). Drop one of each duplicate pair - system-cleaner, windows-tweaks, privacy-tools - and add wpf, dotnet, windows-10. That keeps every distinct search intent covered (disk-cleanup, pc-optimizer, windows-privacy all survive), restores the ecosystem tags, and honours the Windows 10 claim the README already makes. Apply via gh repo edit --add-topic wpf --add-topic dotnet --add-topic windows-10 --remove-topic system-cleaner --remove-topic windows-tweaks --remove-topic privacy-tools, and re-run gh repo view --json repositoryTopics to confirm the count stays at 20.
Rationale
Stars are the maintainer's stated gate for a code-signing certificate, and the star-giving audience for a .NET 10 / WPF showcase finds projects by language-and-framework topic, not by "pc-optimizer". Since the cap blocks any future additions too, clearing the duplicate slots now is what keeps topics adjustable as new features (e.g. bandwidth monitoring, audio mixing) justify new tags.
Evidence
gh repo view laurentiu021/SystemManager --json repositoryTopics -> the 20 topics listed above (counted: 20, GitHub's documented maximum). usesCustomOpenGraphImage: true and a populated openGraphImageUrl confirm the social-preview image already exists - that part of the discovery surface is fine and needs no change. Windows 10 support asserted at README.md:32 ("Runs on Windows 10/11") and by the Platform badge at README.md:18 (platform-Windows%2010%2B). Framework/stack confirmed at README.md:1057-1060 (".NET 10 (WPF, C# 14)", "WPF-UI (lepoco/wpfui)").
Risk / trade-off
Repo-settings change, not a commit, so it needs the maintainer or an authorised write - and dropping a topic loses whatever small traffic it drew. The three chosen removals are each covered by a surviving near-synonym, which bounds that loss.
Affected area
Release
Effort: S | priority: value 3/5, fit 5/5
Identified during the trust, distribution and reach audit audit.
Problem
gh repo view --json repositoryTopicsreturns exactly 20 topics - GitHub's hard maximum - so discovery tags can no longer be added, only swapped, and the current set spends slots on overlaps while omitting the ecosystem tags a developer browses by. Present:csharp, gaming, network-monitor, performance, process-manager, system-monitor, system-utility, uninstaller, windows, windows-11, winget, debloat, disk-cleanup, pc-optimizer, privacy-tools, task-manager-alternative, windows-privacy, ccleaner-alternative, system-cleaner, windows-tweaks. Three pairs are effectively the same query surface:disk-cleanup/system-cleaner,pc-optimizer/windows-tweaks,privacy-tools/windows-privacy. Missing entirely:wpfanddotnet- the two tags through which .NET desktop developers browse GitHub, and the audience most likely to star a portfolio piece - pluswindows-10, even thoughREADME.md:32and the Platform badge both promise Windows 10 support.Proposed solution
Swap, don't append (the cap is already reached). Drop one of each duplicate pair -
system-cleaner,windows-tweaks,privacy-tools- and addwpf,dotnet,windows-10. That keeps every distinct search intent covered (disk-cleanup,pc-optimizer,windows-privacyall survive), restores the ecosystem tags, and honours the Windows 10 claim the README already makes. Apply viagh repo edit --add-topic wpf --add-topic dotnet --add-topic windows-10 --remove-topic system-cleaner --remove-topic windows-tweaks --remove-topic privacy-tools, and re-rungh repo view --json repositoryTopicsto confirm the count stays at 20.Rationale
Stars are the maintainer's stated gate for a code-signing certificate, and the star-giving audience for a .NET 10 / WPF showcase finds projects by language-and-framework topic, not by "pc-optimizer". Since the cap blocks any future additions too, clearing the duplicate slots now is what keeps topics adjustable as new features (e.g. bandwidth monitoring, audio mixing) justify new tags.
Evidence
gh repo view laurentiu021/SystemManager --json repositoryTopics-> the 20 topics listed above (counted: 20, GitHub's documented maximum).usesCustomOpenGraphImage: trueand a populatedopenGraphImageUrlconfirm the social-preview image already exists - that part of the discovery surface is fine and needs no change. Windows 10 support asserted atREADME.md:32("Runs on Windows 10/11") and by the Platform badge atREADME.md:18(platform-Windows%2010%2B). Framework/stack confirmed atREADME.md:1057-1060(".NET 10 (WPF, C# 14)", "WPF-UI (lepoco/wpfui)").Risk / trade-off
Repo-settings change, not a commit, so it needs the maintainer or an authorised write - and dropping a topic loses whatever small traffic it drew. The three chosen removals are each covered by a surviving near-synonym, which bounds that loss.
Affected area
Release
Effort: S | priority: value 3/5, fit 5/5
Identified during the trust, distribution and reach audit audit.