Use GitHub Issues and the repository templates. Good reports include:
- version or commit SHA;
- minimal reproduction;
- expected behavior;
- actual behavior;
- sanitized evidence;
- whether a fixture or benchmark should change.
Do not publish credentials, private telemetry, personal data, or sensitive exploit details in a public issue.
Follow the process in SECURITY.md.
Support focuses on the documented use cases and safety boundaries of this repository.
For security-related projects, requests that materially expand harmful capability, unauthorized access, stealth, credential theft, persistence or evasion may be declined.
When possible, attach or describe a synthetic fixture rather than a screenshot-only report. A reproducible failure is much easier to fix and keep fixed.