Report it privately through GitHub: open the repository's Security tab and choose "Report a vulnerability". Please do not open a public issue for a security problem.

Include the AgentDust version (agentdust version), the macOS version, and the steps that reproduce the problem.

Security fixes go into the latest stable release and into main.

A release is withdrawn when it can signal a process that the rules say it must never signal, or when its artifacts are in doubt. Until the replacement is out, either of these works on your machine:

1. Set apply = false in config.toml in the data directory (~/Library/Application Support/agentdust). Manual and automatic cleanup then refuse every item, and agentdust doctor still works. Run agentdust auto disable in your foreground terminal to clear automatic permissions and remove the worker.
2. Install the previous formula from the tap: brew uninstall agentdust, then brew install hamzahamidi/agentdust/agentdust@0.1, with the previous minor release in place of 0.1.

The steps, and how to check a release with gh attestation verify, are in docs/release.md.

The adversaries AgentDust is designed against, the controls for each and the risk that remains are in the threat model.

• AgentDust signals a process that its rules say it must never signal.
• Manual approval can be completed without the typed code.
• Automatic cleanup signals outside the enabled directory policy or signals a kept, live, shared or uncertain process.
• Data that the design says is never stored (commands, command output, process environments) reaches disk or a model.