Security

• AOT releases ship a SHA-256 checksum manifest (SHA256SUMS) and an Ed25519 signature over it (SHA256SUMS.sig). Checksum verification is mandatory in every installer; signature verification is best-effort in install.sh (needs OpenSSL 3.2+), not attempted in install.ps1, and mandatory on the MCP path.
• The MCP server supports bearer-token authentication for streamable HTTP and validates requested repositories against its configured workspace allow-list.
• The MCP adapter delegates Git and AI work to the existing gitaiflow executable; it does not reimplement or silently broaden the CLI execution model.
• Telemetry remains off by default and, when enabled, excludes repository names, file paths, file contents, diffs, branch names, commit messages, and generated summary text.
• Tools can write artifacts inside the selected repository (change-summary/, CHANGELOG.md, RELEASE_NOTES.md) and local state under ~/.gitaiflow. Keep MCP_ALLOWED_WORKSPACES as narrow as you can, and review generated AI output before sharing it outside your team.

Supported platforms