# Security
Report vulnerabilities privately to the repository maintainers. Do not include credentials,
internal mirror URLs, or production configuration in public issues.
bot-forge treats configuration as trusted executable policy because tool definitions can contain
shell commands. Review configuration before installation and use `bot-forge plan` or
`bot-forge config effective` first. Release scripts require an independently supplied SHA-256 digest for the release checksum manifest. Managed deletion is
restricted to canonicalized bot-forge bin/data and configured agent skill roots.
State and environment writes use atomic replacement. Inspect or abandon incomplete transactions
with `bot-forge resume`; restore APT configuration with `bot-forge apt-mirror restore`.
On macOS, bot-forge invokes an existing Homebrew installation with typed formula arguments and
does not bootstrap Homebrew through a remote shell pipeline.