Skip to content

Security: majormer/SmartFoundations

Security

SECURITY.md

Security Policy

Supported Versions

Only the latest release of Smart! published on ficsit.app receives security and stability fixes. Older versions are not patched.

Reporting Crashes and Stability Bugs

Report ordinary crashes and stability bugs, including save corruption or data loss, through public GitHub issues. A crash or save-related bug does not by itself require private reporting.

Remove sensitive information from public reports, logs, save files, and other attachments. If the information is needed to investigate the issue and cannot be safely shared publicly, use a private channel below to provide it.

Reporting Security Vulnerabilities or Sensitive Information

Report security vulnerabilities privately. Private reporting is also available for sensitive information needed to investigate a bug.

  1. Discord: Send a direct message to Finalomega in the Smart! Discord. Include "security" or "sensitive bug information" as appropriate.
  2. GitHub (security vulnerabilities): Use GitHub's private vulnerability reporting if you prefer a tracked channel.

What to Include

  • Satisfactory version and SML version
  • Smart! version
  • Steps to reproduce, if known
  • Whether the issue affects save files (save corruption, data loss, etc.)
  • Log file from FactoryGame/Saved/Logs/FactoryGame.log

For security vulnerabilities, also describe the security impact. Check all attachments for sensitive information before sharing them publicly.

Response

The maintainer will acknowledge reports as soon as reasonably possible and prioritize fixes that affect save integrity or cause unrecoverable crashes over feature work.

Scope

This policy covers the Smart! mod source code and official releases. Issues in Satisfactory itself, SML, or other mods are outside scope — report those to the relevant maintainers.

There aren't any published security advisories