This fork is security-sensitive infrastructure. We treat MLS state-machine bugs, provider divergence, unsupported ciphersuite negotiation, downgrade acceptance, key-material exposure, storage-boundary mistakes, and dependency drift as security-relevant.

Please report vulnerabilities privately before public disclosure. Use GitHub private vulnerability reporting for this repository when available; otherwise email security@really.me. Do not open a public issue for a suspected vulnerability.

Include the affected crate, version or commit, ciphersuite, platform, and the smallest reproduction you can share without exposing private keys, plaintext messages, production group state, or personally identifiable information.

In scope:

• panics or unchecked error paths reachable through attacker-controlled MLS messages;
• ReallyMe provider behavior that diverges from the reviewed OpenMLS provider contract;
• acceptance of unsupported ciphersuites or unexpected downgrade paths;
• leakage of raw key material, plaintext, credentials, or backend exception text through errors, logs, FFI, or test fixtures;
• dependency upgrades that alter cryptographic behavior without updated tests.

Out of scope:

• cryptographic primitive implementation bugs that belong to the separate reallyme-crypto repository and should be reported through its private security channel;
• unsupported feature or platform combinations that cannot produce a release artifact;
• experimental ciphersuites or draft features that are not documented as production surfaces.

This fork is pre-1.0 from ReallyMe's perspective. Production deployments should pin exact Git revisions, release tags, or package versions and should consume only the ReallyMe-supported provider and ciphersuite surfaces documented in this repository.