RepoGates in October 2026

On Microsoft Edge's own store

The browser extension is on Microsoft Edge Add-ons since 13 October, so an Edge user is no longer sent to a Chrome store page. Edge serves version 0.8.5; 0.8.6 is in Microsoft's review. The Chrome Web Store serves 0.8.6 (as of 14 October). Each store publishes a new version after its own review, so one can be a version behind the other for some days. How to install.

Extension 0.8.5 and 0.8.6

A paid plan is never refused as a trial. Earlier versions kept their own count of the free trial in the browser, and could cancel a subscriber's download with "your free trial has ended". The browser keeps no count now: it asks the service.
A download is never let through because of how its address is spelled. A host written with a trailing dot, or a name written with percent-escapes, is now read as the site serves it. A link that names no repository at all stops with a page that says NOT IDENTIFIED (what to do), never with a made-up name.
A check that fails stops the download at once under your fail mode, where Chrome used to release it after 15 seconds.

No new permission, no new host, nothing new sent in either version. Every version, in full.

Check what you built

The deep scan now works on a public repository you maintain, not only on one you are about to install. Its report ranks what to fix first, a button copies each fix as text for your own coding agent, and a second scan shows what cleared. It is on the report page, in the MCP server (fix_plan) and in the Claude Code plugin (/repogates:fix-my-repo).

RepoGates never changes your code. A scan reads the code and never runs it. A list with nothing left on it is not an audit. Private repositories are not scanned.

We ran the whole loop on ten public repositories we do not own, four of them written to be vulnerable, and published the table, including what a fix made worse and how that text was rewritten: the measurement. Not measured: no repository's tests were run, so whether an application still works after its fixes is not known.

Skills: what they say beside what they do

A new check on AI-agent skills and Claude Code plugins (S16) compares what a skill's description and allowed tools say with what its scripts and hook commands do: a network request, a read of a secret store, a step that survives a reboot. It compares two texts by fixed word lists; it does not read what the code means. A gap alone is a note on an established listing and a finding on a new one, and it never blocks by itself. Measured on 597 listings from skills.sh and Anthropic's two plugin marketplaces: ten notes, no verdict changed.

A dev container's own set-up script warns

On 13 October the deep scan blocked two well-known Python libraries over one finding each: their dev container installs a tool by piping a download into a shell, the usual way. The ordinary check already warns on a dev container, because it runs on its own when a folder is opened in one. The deep scan now does the same, but only for that one rule and only when the script is the dev container's own and nothing else in the repository starts it. A miner, an exfiltration or a reverse shell there still blocks, and the finding is a warning, never a pass.

What's coming

Being built, with a date: the Team seat model, three to five seats on one invoice, for December 2026. It is not on sale until its gate passes; until then, buy Personal per developer.

Decided, not dated yet (a date is set when one is being built, never before):

MCP servers as a marketplace of their own: a server in the official registry assessed like a repository or an extension, from how its namespace was verified to the package it actually launches.
Open VSX, the registry VSCodium, Cursor and Windsurf install extensions from.
Watching what you already installed: the agent check-up's findings re-checked when you look at them, with what changed since the last look.
Check-up readers for Cursor, Windsurf, Codex, Gemini, Cline and VS Code, which today are detected but not read.
A command line for people (repogates clone, repogates check) that refuses a blocked clone or install at a terminal. Only what runs through it is seen.

What has not changed

The browser extension stands at the moment a download starts in your browser. It does not see 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. The plugin sees Bash tool calls in that one client and does not see anything else. VS Code and Docker Desktop extensions and AI-agent skills are answered through the MCP server and the plugin, not in the browser. An agent that never asks the MCP server is not stopped.

What is being built next, with the date and the gate each piece must pass first, is on the roadmap. Questions or a false positive: support@repogates.com reaches a human.