If you believe you have found a security issue in Pyre, please do not open a public issue with full exploit details.

Instead, contact the maintainer privately and include:

• a description of the issue
• affected components or files
• reproduction steps or a proof of concept
• impact assessment, if known

You should receive an acknowledgement and follow-up once the report is reviewed.

Security-sensitive areas include:

• bridge framing and codec handling
• cross-runtime process startup and shutdown
• package and release artifacts
• any future network-facing runtime configuration