Nimblegate
github.com/nimblegate/nimblegate- Category
- Developer Tools
- Rank
- No. 1998Tools index
Previous survey · No. 1944 ·
- Type
- TOOL
- Use case
- Security & Identity
- GitHub
- 3 stars
- Latest release
- v0.6.3
- Date
About
Nimblegate is a self-hosted proxy that sits between an AI coding agent and the real git host, checking every push an agent makes against configured rules before forwarding it. Pushes that pass are forwarded to the upstream host in under a second while unsafe ones are blocked, and every decision is recorded, giving teams a consistent audit trail for agent-driven commits.
At a glance
Nimblegate checks Git pushes on their way to an upstream repository. It is worth considering when coding agents push changes and you need the same checks to reject forbidden changes before they reach the host.
Good fit
Teams that can route agent pushes through a gateway and want a rule, file and line when a push is rejected.
Consider something else when
Skip it if agents can still write directly to the upstream and you cannot close that bypass.
Start here
Start with the public sample dashboard to see how a rejected push is explained. For a later trial, use a disposable repository and a synthetic violation to check that the push is blocked before it reaches upstream.
Cost and requirements
The project documents self-hosting in Docker and free noncommercial use under PolyForm Noncommercial 1.0.0. Check the licence for your intended use. Setup requires access to configure the gateway and upstream repository.
Limits to know
Checks cover enabled rules and pushes sent through the gateway. Review the gateway’s access to repository contents and upstream credentials before routing real projects through it.
Sources checked 2026-11-05. Source-based assessment.
Why it made the leaderboard
Nimblegate sits between an AI coding agent and your real git host, blocking unsafe pushes and forwarding safe ones with a logged decision trail, directly addressing risk from autonomous agent git access.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.