Security / Responsible reporting
Security
Do not post sensitive vulnerability details in a public issue. Flint’s existing SECURITY.md is the source of truth for the project’s reporting guidance.
Starter policy · Last reviewed 13 September 2026Reporting
Flint does not currently publish a security email or hosted disclosure channel. Use the repository host’s private security-reporting feature when one is available. If no private channel is configured, report publicly only that private coordination is needed and withhold exploit details, credentials, tokens, private server addresses, and other sensitive data.
What not to share
- Credentials, passwords, tokens, private keys, or .env contents
- Private server addresses or identifying profile data
- Live exploit steps in a public issue
- Runtime profiles, instance data, or logs that have not been reviewed and redacted
Current boundaries
Downloads use HTTPS and published artifacts should be checked before execution. Profiles use isolated mutable game directories and managed-mod manifests. Existing installations and mod metadata are treated as untrusted input.
AutoAuth is opt-in, uses the Windows-native keyring for passwords, and is intended only for exact configured offline-mode servers. It does not defend against another malicious process already running as the same Windows user. Keep it disabled on untrusted servers.
Project guidance
Read the current SECURITY.md on GitHub before reporting; repository guidance may be updated after this site.