Seventeen genres organize 183 source-labeled links
The README divides games into 17 genre sections, from action and adventure through tower defence and turn-based strategy. Across those sections it contains 183 links explicitly labeled as source. The number includes engine links and nested source-port references, so it should not be read as a game count. As a browsing page, the structure works: a reader can jump to racing, roguelikes, role-playing games, or another familiar category and begin opening candidates.
The scope is wider than the title first suggests. Original games such as Endless Sky sit alongside engine recreations, decompilations, source ports, and remakes of commercial releases. ScummVM is an interpreter for supported adventure games, OpenMW rebuilds the Morrowind engine, and several Doom entries preserve or extend older code. That mix is useful for discovery, though source availability does not guarantee that the original art, audio, levels, or data files may be redistributed with it.
Curation follows one maintainer's personal bookmarks
The contribution guide gives 8 practical rules after its opening policy. A contributor checks for duplicates, chooses a section, keeps titles in lexicographic order, follows one link format, and submits a separate pull request for each game. The first rule is more important: these are the maintainer's personal bookmarks, and a submission is added only if it seems interesting to that maintainer. This is candid curation, with no claim of neutral or complete coverage.
That policy explains both the charm and the limit of the project. Descriptions are usually one sentence, selected by a person rather than generated from a database. Some entries name an engine or original title; many do not. The list links to GitHub, GitLab, Codeberg, SourceForge, Bitbucket, SVN, project sites, and forums. A reader gets breadth, while verification of ownership, licensing, builds, and release status happens after leaving the page.
What happened when we ran it
Our sandbox installed commit 3a9ab8f in 15 seconds, adding 35 packages and occupying 37 MB. The harness build step succeeded in 5 seconds inside an unprivileged Debian container with 3 CPUs and 8 GB of RAM. The checkout contained 4 files and about 54 lines of source, with its measured size rounded to 0 MB. That small footprint is expected because the 37,285-byte README carries the actual directory.
There was no tests script or target, so our harness skipped tests. Pip-audit found 0 known vulnerabilities in the installed Python environment. Those outcomes apply to the tiny local utility environment, not the 183 linked source destinations. The repository had no CI workflow, no Dockerfile, and no tests directory. Nothing in our run checked whether a game site loaded, a source URL still existed, or a linked project built.
The only Python file is a 1,541-byte helper named coauthor.py. It calls the GitHub user API and prints a Co-authored-by line for a commit message. That explains why a Python environment can be installed and built, but the script does not parse the README or inspect links. A useful test plan for this repository would begin with URL status and duplicate checks, neither of which the current four-file checkout automates.
Programming language and platform filters are absent
Issue 71 asks for a programming language beside each game because readers currently have to open most source links to learn it. The maintainer replied on February 25, 2026 that there was no time to add the data and invited someone else to submit a pull request. A later comment points to the Trilarion catalog, which already stores language metadata and supports filtering on its website.
Platform, license, engine, activity, asset requirements, and playability have the same consistency problem. A description may mention Windows, Linux, Android, Godot 4, or SDL3 when a contributor included it, but there is no required field set. Issue 120 suggests Luanti, and issue 118 suggests Mindustry even though Mindustry already appears under real-time strategy. Open suggestions therefore need human duplicate and placement review before they improve the list.
The README last changed on February 25, 2026
GitHub recorded the last push on February 25, 2026, when several entries and formatting fixes landed. The repository showed 13,855 stars and 28 combined open issues and pull requests when fetched. Issue conversations continued into September, including proposed additions, so reader interest has outlasted the latest merge burst. There are no GitHub releases, which is reasonable for a README directory but leaves no dated catalog snapshot beyond commit history.
Use open-source-games when a plain genre list is exactly what you want. It is faster to scan than a database interface, CC0-1.0 covers the list itself, and the contribution rules are easy to understand. The 183 source labels still require individual research. Check the linked project's current repository, license, required commercial assets, supported systems, releases, and issue activity before choosing what to play, study, or contribute to.