Leonida builds everything from the player's own copy, so the two things that can hurt the project are a security bug in the tools and game data that reaches the repository. This page covers both.
Never put the details in a public issue, pull request, comment or Discord channel. Quoting the problem in public spreads it further.
- Preferred: the repository's Security tab → Advisories → Report a vulnerability. Only the maintainers see it.
- If that button is missing: ask a maintainer for a private channel on Discord. Your first message should say only that you have something to report, with no details.
Say what you found, where (file, commit, pull request or issue number) and when you noticed it. Don't attach the file itself.
This covers everything CONTRIBUTING.md rules out: archives, the executable or DLLs, carved files, shaders in any form (DXBC, FSSM, disassembly, SPIR-V), textures, models, audio, videos, keys, and logs or reports that quote any of them. It applies wherever it shows up: a commit, a branch, a pull request, an issue or a comment attachment.
If you see it: report it privately as above. Don't download it, mirror it, fork the repository to keep it, or comment on the pull request or issue that holds it.
If you pushed it yourself:
- Report it privately right away, even if you have already deleted the file. A later commit that deletes a file leaves it in the history.
- Don't push again to fix it, and don't open another pull request. The maintainers rewrite the history once.
- If it is in your own fork, delete the fork or clean it the same way.
What the maintainers do:
- Close or merge the open pull requests that touch the affected history, then rewrite every ref with
git-filter-repo (2.47 or later,
--sensitive-data-removal,--invert-paths --path <file>for each path the file ever had) and check that the data is gone. - Force-push with
git push --force --mirror origin. Pull request refs are read-only and keep the old history. - Ask GitHub Support to dereference or delete the affected pull requests and to remove cached views. Give the repository name, the number of affected pull requests and the first changed commit from the git-filter-repo output.
- Ask the owners of forks that contain the commits to delete them.
- Hide or delete issue and comment attachments that hold the data.
- Tell contributors to re-clone or rebase onto the new history. A
git pullandgit pushfrom an old clone puts the data back.
The tools and the runtime read large binary files and run external programs (git, llvm-mc, spirv-as,
ffmpeg). In scope:
- A file in a game folder that makes a tool write outside
--outor--work, or run a command it shouldn't. - Unsafe parsing in
tools/orruntime/(for exampleeval, path traversal, or unchecked sizes and offsets). - The build downloading or running anything other than the pinned
third_party/rpf9-explorersubmodule. viewer/serve.pybeing reachable from anywhere but127.0.0.1.- CI workflows that expose tokens or run untrusted code with write access.
Out of scope: the game itself, Xbox or Rockstar services, and any copy protection. Leonida does not work around protection, and reports that ask it to are closed.
Only the latest main gets fixes.