aftlog is currently an MVP. Security fixes are applied to the latest code on the main branch; older commits and locally modified builds are not supported.

Please do not open a public issue for a suspected vulnerability. Use GitHub's private vulnerability reporting to share the impact, reproduction steps, affected platform, and a proposed fix if you have one.

Do not attach live credentials, private agent transcripts, or an unredacted aftlog session directory. Replace sensitive values with synthetic examples.

Reports involving redaction should include the smallest synthetic command or event payload that reproduces the leak, plus the affected report format (Markdown, JSON, or HTML).

Keep these boundaries in mind when evaluating or deploying aftlog:

• The daemon is intended to listen on loopback. Its hook endpoint has no authentication and must not be exposed to an untrusted network.
• Raw hook events and transcripts can contain sensitive local data. aftlog's rendered redaction and secret scanning are best-effort, not a secure vault or a proof that logs are secret-free.
• Revert applies changes to the recorded working directory. It requires an explicit --confirm, creates backups where possible, and can still conflict with changes made after a session.
• aftlog records evidence; it does not sandbox agents, enforce permissions, or prevent a malicious command from running.