Please do not open a public issue with exploit details.
Instead:
- contact the project maintainers privately through the security reporting channel used for OpenMinion, or
- if that channel is unavailable, open a minimal private coordination thread without exploit details and request a secure handoff path.
OpenMinion's security posture follows these rules:
- report vulnerabilities privately first,
- do not publish proof-of-exploit details before maintainers have had time to assess and respond,
- include affected version, reproduction steps, and impact summary when possible.
Reports should say whether the issue affects:
- the public standalone package surface documented by
README.md,API_COMPATIBILITY.md, anddocs/, - package-owned CLI, API, runtime, tool, or example surfaces in this repo, or
- deployment-specific, third-party, or operator-owned infrastructure outside the package contract.
If the issue depends on a specific provider, transport, database, plugin, browser automation backend, or host deployment shape, call that out explicitly. That helps determine whether the bug is in the package-owned framework surface or in an integration/deployment path around it.