How RepoGates works, what it covers, and how to use it — in your browser and in the AI agents that are told to ask it first.
Install the extension in Chrome or Edge, activate it, and read your first verdict on a repository page.
Install and activate →The trust board on GitHub, Hugging Face and GitLab pages, the gate on downloads, and allowing something once or always.
The trust board →Connect Claude Code, Claude.ai, Cowork or any MCP client so an agent asks before it clones or installs.
Connect your AI agents →A deep scan of a repository's files in a sandbox, and the check-up of what your AI agents already have installed.
Deep scans →Every published check, how a decision is made, what exists today, what changed in each version, and troubleshooting.
The checks →The campaigns and techniques RepoGates was built against, each with its sources.
FakeGit and the rest →preflight), a package named on it —
npm install express, pip install flask —
resolved to the repository it declares; the
Claude Code plugin's hook
refuses a blocked line before it runs; the
skill makes Claude.ai and
Cowork ask first.git clone, package managers or
curl — outside Claude Code with the RepoGates plugin,
whose hook refuses a clone or install that names a blocked
repository on the command line, before it runs. A browser
extension cannot see other processes; that is structural, not a
roadmap item.curl is not stopped. In Claude.ai
and Cowork the skill is the same — advisory.Read,
not MCP git tools, not another agent, not a human at a
terminal. Edit and Write are read for one thing only — an API
key about to be saved — checked on the machine and never sent;
that guard asks, it never denies.Questions, bug reports, false blocks, security disclosures and
procurement all reach the same human:
support@repogates.com.
For a false block, include the owner/repo and the check
names shown on the decision page — that is everything we need.
Related: Changelog: every release of every product · Privacy · Pricing · How we measured ourselves · Honest coverage.