Security
What Yapnap does to keep you safe, and what we cannot promise. The app has the same page under Security in its settings.
What we check
- Mods are data only. A mod is a name, a description and CSS. It cannot run code, read the page, load a file or reach the network.
- Mods are checked twice. The website checks them before they are listed, and the app checks them again before they are kept.
- Downloads are verified. Each mod must match the fingerprint in the list. The list and the mods only come from yapnap.pages.dev over HTTPS, and redirects are refused.
- The app's page is sandboxed. Yapnap's code runs with context isolation, and Node.js is not reachable from Yapper's page.
- Changes that matter need a click. Installing a mod, roles, the role key, sign-out and importing files cannot be done by a script on the page alone.
- Packaged builds are hardened. Electron's fuses turn off running the app as a Node tool, and the app only loads code from its own archive.
- Safe mode. Turns off every plugin, mod, theme and custom CSS at once.
What we cannot promise
- Code signing. The Windows app is not code-signed yet, so Windows may warn before it runs. Compare the file's SHA-256 with the one on the release page.
- Independent audit. Nobody outside the project has audited Yapnap. These checks are ours.
- Yapper's website. Yapnap runs inside Yapper's website. If that site were compromised, Yapnap could not protect you from it.
- Machines without a keychain. Where the system has no keychain, the role key is only protected by your account folder.
Found a security problem? Tell us on GitHub. Please keep exploit details private until it is fixed.