OrganoidOS is currently at v0.1 draft. We will backport security fixes to the latest published release only. Once v1.0 ships, the policy below applies.

If you discover a security issue, please do not open a public issue.

Email: security@organoid-os.example (placeholder — until we have a real maintainer email, please DM a maintainer directly via GitHub).

Please include:

1. A description of the issue and its potential impact
2. A minimal reproduction (a script, or a description of the input)
3. Affected versions
4. Any suggested remediation

We will acknowledge receipt within 3 working days and aim to publish a fix within 30 days for medium-severity issues, faster for critical ones. We will credit you in the disclosure unless you prefer to remain anonymous.

OrganoidOS is a research project. The reference emulator does not execute arbitrary code, does not connect to the network, and does not read files outside the working directory. The main security concerns are:

1. Pickled snapshots. MigrationSnapshot.to_json() and restore_to_organoid() use JSON, not pickle. Do not add pickle support without a sandboxed loader. A malicious snapshot could otherwise execute arbitrary code on restore.
2. Driver plugins. When L1/L2 drivers are contributed, they will load vendor SDKs. Those SDKs are out of scope for this security policy; users are responsible for trusting the drivers they install.
3. Closed-loop protocols. When run against real wetware, the scheduler can apply stimulation patterns. A buggy or malicious Task.reward_fn could in principle drive harmful stimulation. Labs running on real cultures MUST run with a hardware-level stimulation intensity limiter independent of this software.
4. Supply chain. We pin numpy only. Be cautious when installing any optional dependency.

• Vendor SDK vulnerabilities (report to the vendor)
• Wetware welfare issues (these belong in docs/ethics.md, not security)
• Research correctness bugs that don't have a security dimension (use a normal issue)

We follow coordinated disclosure. Once a fix is released, we will publish a SECURITY-ADVISORY-YYYY-NN.md in this repo describing the issue, affected versions, and remediation, crediting the reporter unless they prefer anonymity.