Please report security issues privately through GitHub's vulnerability-reporting / Security Advisory flow when available. If that is not available, open a minimal public issue asking for a private contact path without including exploit details or sensitive data.

The latest release is the primary supported version. Older releases may not receive security fixes.

Security-relevant areas include parsing and writing the mod settings file, hardware-detection subprocesses, numeric/range validation before values reach FS25, path handling, and any case where untrusted local input could cause unintended command execution or file access.

A poor VRAM recommendation, unsupported GPU, or a game crash caused by an overly aggressive user-configured budget is normally a correctness/compatibility issue rather than a security vulnerability unless it crosses one of those trust boundaries.

• Hardware detection is best-effort and runs only the documented local detection paths.
• The recommended budget is a conservative heuristic, not a guarantee that a particular game/mod workload cannot exhaust VRAM.
• A manually edited settings value is user input and is not evidence that the helper selected that value.
• Release assets are not code-signed; verify published checksums when provided.

Please redact machine names, usernames, paths, serials, logs, or other personal/system information that is not needed to reproduce a report.