CS2Bugs imports issues from ValveSoftware/csgo-osx-linux, the public tracker Valve uses for Counter-Strike bug reports, and presents them with filters the GitHub UI does not make obvious.
What the data is
Every field on an entry comes straight from the GitHub API. Nothing is scored, ranked or assessed by hand:
- State — Open or Closed, exactly as GitHub reports it. Entries also carrying the
wontfixlabel are shown as Wont Fix. - Platform — from the
WindowsandLinuxlabels. An issue can carry both. - Component — from labels like
Audio,AnimationandUser Interface. Issues with no component label are listed under Gameplay. - Upvotes — the thumbs-up reaction count on the issue.
- Comments — the thread length, often a better signal of how live a problem is than upvotes.
What it deliberately does not do
There is no severity rating. Assigning Critical or Low would mean inventing a judgement the tracker does not contain, so the real signals — upvotes, comment count and last activity — are shown instead and you can draw your own conclusion.
Descriptions are truncated excerpts of the issue body with the report-template scaffolding stripped out. They exist to help you scan; the full thread, screenshots and any Valve response live on GitHub, and every entry links to it.
Scope
Only issues opened on or after 27 September 2023, the CS2 release date, are included. Older reports on that repo belong to CS:GO. Issues labelled invalid, duplicate, question or enhancement are skipped, as are ones whose body is too short to summarise.
The repo is named csgo-osx-linux for historical reasons but is where Windows reports are filed too, which is why the Windows listing works at all.
Freshness
The listing is a static snapshot rebuilt when the import is re-run, not a live feed. Check the source issue on GitHub before treating any state as current.