PanludiaBEHIND THE DIRECTORY
Evidence.
Not a guarantee.
We make the available evidence easier to understand. We do not turn a directory listing into a security certificate.
Six things worth knowing
The limits of a reviewSource review, not blanket certification
Our community reviews cover available documentation, repositories, releases and reported issues, with targeted static inspection where useful. We do not claim complete code audits, malware analysis or runtime testing for every integration.
Confidence is not a guarantee
A confidence label describes the available evidence. Playable means a downloadable build exists, not that every option combination has been tested. Neither label guarantees malware-free software, bug-free play or safety for every save.
A hash identifies bytes
When an inspected artifact is recorded with a SHA-256 hash, the hash identifies that exact file. It does not prove that the file is harmless or that a published binary matches its source code. A newer file needs its own assessment.
Know what was actually tested
Documentation review, static inspection and a real-game test answer different questions. Tests of Panludia's website are not tests of the mods it lists. Our own development process, described in The forbidden methodâ„¢, must not be assumed to apply to independently maintained integrations.
Use the maintainer's instructions
Check the exact game and integration versions, read known issues and back up your saves before installing. Use the original release and setup documentation linked on the project page. Do not publish room passwords, tokens or private save data in reports.
Reviews are a snapshot
A review date states when evidence was assessed, not a promise of continuous monitoring. New releases, game updates and new reports can change compatibility or reveal problems that earlier checks did not find.