A GitHub Trending snapshot on October 3 counted 1,837 new stars in a week for AnyPS5. On that same date, the project's compatibility table contained one game. Developers have produced a working route from a PlayStation 5 executable to a native PC binary, yet the public evidence still covers a single 2D title on Windows. The attention has moved much faster than compatibility.
The repository passed 3,200 stars by October 4, roughly two months after it was created. Its pitch is unusually direct: feed a clean PS5 ELF executable into a relinker and get an ELF for Linux or a PE executable for Windows. No console emulator stays open beside the game. The project supplies reimplementations of system libraries and translates shaders for Vulkan. Those pieces are substantial. They also leave a large surface where one missing function, instruction, or assumption can stop a game at launch.
What "automatic porting" does here
AnyPS5's usage guide describes a conversion pipeline rather than a one-click game installer. The input directory needs the game's clean ELF and its bundled modules. The output needs the project's replacement PRX libraries in a libs directory and game resources under app0. The two basic conversions are short enough to fit in a terminal:
relinker source/input.elf app.elf
relinker --windows source/input.elf app.exe
The .exe suffix alone does not select Windows output. An explicit flag does. The relinker can also scan imports, convert supported AMD-only CPU instructions for Intel hosts, and write a registry file that records its work. Unsupported conversions stop with an error instead of leaving a partly patched instruction behind.
Native output changes where the engineering work goes. CPU code can run as host code after its executable format, imports, and platform assumptions are repaired. Calls that once targeted PS5 system libraries land in the project's own dynamically linked implementations. GPU programs take another path: AnyPS5 recompiles console shaders into SPIR-V for Vulkan. The project dashboard counted 2,452 implemented library functions and 852 recognized shader instructions when checked on October 4.
The repository does not include Sony firmware, cryptographic keys, proprietary libraries, or games. Its README says users must obtain and use their own binaries according to applicable law and licence terms. That boundary matters because the relinker itself is GPL-2.0 code, while the material people may try to process with it can have entirely different rights and restrictions.
One row sets the current ceiling
The verified compatibility list has one entry: Dreaming Sarah, game ID PPSA02929. It is marked "in game, playable" on Windows. Linux is a question mark. The table records 60 frames per second on a GTX 1050 Ti with an i5-7500 and 36 fps on Intel HD Graphics 620 with an i5-7200. That is a concrete result on modest hardware, and it is far narrower than the repository description may suggest to a casual visitor.
The progress badges need the same careful reading. System libraries show 77.25 percent, but the denominator contains only functions already declared in the repository. The project warns that this is not a count of every function available on a PS5. A function counts as implemented once it no longer calls the project's NotImplemented_nid_no_patch failure path. That metric tracks source coverage. It cannot show that every implemented function behaves correctly for every game.
The shader badge reports 73.07 percent across an RDNA 1 and RDNA 2 instruction list. Here, an instruction counts when the decoder recognizes it. The dashboard therefore measures decoder coverage, not the number of games that render correctly. A title can depend on an instruction that is present but behaves differently in a particular shader, or it can reach a system-library path that the one verified game never touches.
AnyPS5's technical-debt log puts names on those gaps. The headset library reports a disconnected device and has no tracking or rendering. The player-invitation dialog completes without showing an interface or sending an invitation. Intel conversion does not lower every AMD-specific instruction form, and some trampoline paths have only synthetic tests. These are useful disclosures because a broad percentage can hide the exact function that a new title needs.
Failure is part of the design
The project takes a strict approach to unfinished behavior. Its README says unsupported or unexpected states throw a C++ exception, print the error, and terminate the process. The contribution rules require each function either to do what its contract demands or to throw. Silent stubs are allowed only for user-interface behavior that unblocks a title, and maintainers record them in the debt log.
For users, that policy means an unhandled function can end a session abruptly. For developers, it produces a useful failure address instead of allowing bad state to spread through audio, graphics, saves, or networking. Compatibility work benefits from that honesty. A game that reaches its first menu through dozens of fake success returns may look better in a screenshot while telling maintainers less about what actually works.
The rule also explains why one verified title can coexist with thousands of implemented functions. A modern game reaches a particular slice of the console API. Another title, even on the same engine, may ask for a different shader instruction, dialog path, file-system behavior, or network call. Native execution removes the cost of emulating a CPU, but it does not remove the need to reproduce the platform around that CPU.
A release you can download, with a narrow setup path
AnyPS5 is further along than a proof-of-concept repository with screenshots. Version 0.1.1, published on September 28, includes relinker binaries and separate Linux and Windows PRX bundles. Its release notes list work on fonts, save data, an offline socket and resolver stack, video playback, shader operations, and runtime layout. The tag followed v0.1.0 by less than two hours.
The setup is still aimed at developers. Source builds require x86-64, CMake 3.22.1 or newer, Ninja, and a C++20 compiler. Windows builds support one specified MinGW-w64 GCC 15.2.0 package, according to the build instructions. Configuration may download FFmpeg binaries unless the builder supplies them. There is no launcher that locates a game, checks its modules, converts it, and arranges every output file.
Continuous integration does more than compile the relinker. The build workflow runs Linux and Windows jobs, builds the replacement libraries, and repeats the test suite three times. The Linux job installs a software Vulkan driver for GPU execution tests. That catches deterministic build failures and some shader regressions. It cannot substitute for running more commercial titles, which the compatibility file makes plain.
Stars have created a second scaling problem
The October 4 repository snapshot showed 1,216 commits and more than 130 open pull requests. That volume can fill missing API calls quickly, but low-level compatibility code is hard to review from a diff alone. A patch may compile on both hosts and still encode the wrong calling convention, GPU rule, timing behavior, or error value. The repository's test policy asks contributors to identify the operating system and title or homebrew they tested.
The same policy requires contributors to disclose AI assistance and makes the pull-request author responsible for every line. That is a practical rule for a project receiving many small implementations at once. Generated code can reproduce a familiar POSIX function and still miss a console-specific ABI detail. The debt log already records unknown signatures and unnamed exports, so reviewers sometimes have incomplete evidence even before automation enters the workflow.
More contributors can expand the test matrix if they bring lawful binaries, different hardware, and reproducible reports. They can also leave maintainers with a queue that grows faster than anyone can validate title behavior. The repository's strict failure policy, cross-platform CI, and written debt list give reviewers a basis for saying no. The one-row compatibility table shows where automated checks currently stop.
The clearest next milestone is plain: a second row in COMPATIBILITY.md, preferably one with a Linux result instead of ?. After a week that added 1,837 stars, another verified game would say more about AnyPS5's reach than another thousand stars. Until that row arrives, AnyPS5's demonstrated reach remains one Windows game.