C# repositories

Every public repository surveyed, browsable and searchable. Including the unflattering ones — a tool that only published good results would be a badge vending machine, not a diligence instrument.

All bands Strong Adequate 42 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
nlog/nlog 4 strong C# 162,867 lines 6,548 2026-10-25 strong
btcpayserver/btcpayserver 3 adequate · 2 strong C# 203,741 lines 7,823 2026-10-23 adequate
quartznet/quartznet 1 adequate · 4 strong C# 608,055 lines 7,092 2026-10-23 strong
umbraco/umbraco-cms 3 adequate · 2 strong C# 1,420,731 lines 5,279 2026-10-25 adequate
nager/nager.date 1 adequate · 3 strong C# 48,408 lines 1,439 2026-11-03 strong
iotsharp/iotsharp 3 adequate · 2 strong C# 470,263 lines 1,384 2026-11-03 adequate
drasi-project/drasi-platform 1 adequate · 4 strong C# 124,690 lines 1,256 2026-11-03 strong
onlyoffice/communityserver 3 adequate · 2 strong C# 1,405,552 lines 3,171 2026-10-23 adequate
skyapm/skyapm-dotnet 4 adequate C# 24,699 lines 1,658 2026-10-28 adequate
featbit/featbit 3 adequate · 2 strong C# 314,467 lines 1,946 2026-10-23 adequate
smartstore/smartstore 3 adequate · 2 strong C# 664,109 lines 1,736 2026-10-23 adequate
sev7enup/nodepilot 3 adequate · 2 strong C# 569,476 lines 102 2026-10-25 adequate

What a band means. A band sums up one reading of one commit: strong, adequate or significant findings. Here it counts the project's code, process, product, security and operations. A report reads more than that, so its band can differ from its row.

How listing works. Every public repository surveyed is listed — assessing public work is commentary on public work, and a library that hid the small ones would be quietly editorialising about which code counts. Private repositories are never listed. Anyone who proves control of a repo can attach a response to a finding, request a re-run, or delist it. Delisting is immediate and no-questions. An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev. There is no org-level score. Repositories are listed one by one, and sorting by band orders them by their own readings. Takedown: one email, 48 hours.