Security
How to report a vulnerability in Airpost, what is in scope, and how Airpost handles your credentials.
Reporting a vulnerability
Report vulnerabilities privately through GitHub’s private vulnerability reporting:
github.com/airpost-mail/airpost/security/advisories/new
Airpost has no security email address. Please don’t open a public issue for a vulnerability.
Include what you can:
- The affected component: desktop app, engine, CLI,
airpost-mcp, server, or web client. - The version or commit.
- Steps to reproduce.
- The impact you expect.
Reports about a download site that hosts modified or malicious builds under the Airpost name are welcome through the same form.
Scope
Everything in the Airpost repository is in scope.
Third-party plugins and themes are fully trusted code once installed (see Plugins overview), so a plugin doing what any local program can do is not a vulnerability in Airpost.
How Airpost handles your data
The desktop app and its engine run on your machine. Mail account credentials are encrypted with the OS keychain (Electron safeStorage, keychain item “Airpost Safe Storage”) and are only handed to the local engine. The engine’s socket accepts connections from the same local user only.
An Airpost server you sign in to gets an account’s credentials only when you choose to sync that account on the server too. There they are held by the server’s engine, never by its account or web layers. See Architecture and Self-hosting security.