Security by boundary, not by promise
Give AI the repository access it needs. Nothing more.
Secure Git Bridge creates a controlled bridge between an AI coding assistant and a repository explicitly approved by the developer. Repository authority stays local and every AI-reachable operation passes through the same boundary and policy layer.
Repository isolation
Each AI connection is pinned to one approved repository capability. A conversation cannot enumerate, select, switch to, or cross into another saved repository through Secure Git Bridge.
Protected files
Protected-file rules block secrets, key material, Git internals, and customer-defined deny patterns from AI-facing reads and diffs. The AI cannot change the policy that constrains it.
No direct AI repository writes
AI clients can inspect approved code and create patch proposals. Applying a proposal remains a privileged local human action; Secure Git Bridge does not expose an AI-facing tool to approve or apply patches.
Local audit trail
Repository access decisions and AI operations are recorded locally. Commercial licensing services do not need repository contents, Git credentials, repository paths, prompts, or AI-provider credentials.
What can leave the Mac
When you authorize an AI assistant to inspect approved repository content, that content is sent to the AI provider you configured. Secure Git Bridge does not claim that approved code never leaves your machine; it enforces which repository content the AI connection is allowed to request.
Commercial service boundary
The Secure Git Bridge commercial service handles licensing, plan, billing, account, organization, and bounded device metadata. Repository contents and AI-provider credentials are outside that commercial service boundary.
Release integrity
macOS releases are Developer ID signed, Apple notarized, stapled, and published with a release manifest and SHA-256 digest. Customers should install only packages obtained from securegitbridge.com. Verify the current release →
Report a security issue
Send vulnerability reports to security@securegitbridge.com. Please do not include production credentials or unrelated customer data in the initial report.