Only the latest 0.1.x beta release is currently maintained.
Use GitHub's Report a vulnerability flow in the repository Security tab. Do not open a public issue containing secrets, private replay artifacts, credentials, exploit details, or user data.
- Process replay is not a sandbox and must not run untrusted artifacts.
- Docker replay drops capabilities, uses an unprivileged user and read-only root filesystem, limits resources, and disables networking by default; it is defense in depth, not a complete isolation guarantee.
- Dependency installation executes package build/install code and is disabled unless explicitly enabled.
- Environment collection uses an allowlist and secret-shaped name rejection, but users must inspect artifacts before sharing them.
- Network capture is metadata-only. Packet payloads are never intentionally collected.
See docs/threat-model.md for the detailed model.