Skip to content

Security: Bedriox/Runtime

Security

SECURITY.md

Security Policy

Do not publicly disclose a suspected vulnerability in Runtime, its download or archive handling, native dependencies, packaging, certificate configuration, or release workflows. Contact the Bedriox maintainers privately through the security reporting channel published by the Bedriox organization.

Include the affected commit or release, target platform, reproducible steps, and impact. Remove credentials, private keys, tokens, private paths, and player data before sharing diagnostics.

Only artifacts attached to an official Bedriox Runtime release and matching its published SHA-256 checksum are supported. A build from an unreviewed fork or an artifact whose checksum does not match should be treated as untrusted.

There aren't any published security advisories