Troubleshooting

The questions people actually ask about RepoGates, with the answer and what to check.

"A download went through without a verdict"

Two honest facts first, because they explain almost every case:

  • Chrome gives a download listener at most 15 seconds, and on expiry it fails open — the download proceeds. RepoGates budgets its whole decision at ~8 seconds to stay inside that, and runs a backstop that re-checks a download already in progress and cancels it late rather than never (those show as late-blocked / late-warned in the audit log). A slow machine plus a cold service worker can still lose the race. This is a browser platform ceiling, not a setting.
  • Bytes stream to a temporary file while RepoGates deliberates. A block stops the file reaching your downloads folder and discards the partial temp file — it does not mean the bytes never touched disk, and we do not claim otherwise.

Then the ordinary explanations, in the order to check them:

  1. The URL is not one RepoGates gates — it covers GitHub repository archives, release assets and raw files; it does not gate non-GitHub hosts or git clone.
  2. You saved the page with Save Page As (Ctrl/Cmd+S) — on a raw file, for example. Chrome writes a saved page without giving extensions the hold it gives a download, so nothing is held. In extension 0.8.3 such a save was not gated at all. Since 0.8.4 (on the Chrome Web Store as of 30 September 2026) RepoGates checks it as soon as Chrome starts writing it: a file still being written is cancelled; a file already written (a small one is written in well under a second) is deleted, wherever you saved it, and recorded as removed-blocked or removed-warned. The bytes do reach your disk until then. A page saved from a view that is not a download (a file's blob view, an issue page) is not gated.
  3. RepoGates is paused (Options → Protection).
  4. The repository is on your allowlist.
  5. You already proceeded or overrode for this repository this browser session.
  6. Your fail mode is open and the service was unreachable.

The audit log tells you which of these happened — every allowed path is logged with its reason.

Extension 0.8.4 and earlier kept their own count of the free trial in the browser, and nothing told them your account had paid. On a download the extension had not checked before, your eleventh repository or any download 30 days after installing could be cancelled with "You have assessed your 10 free-trial repositories" or "Your 30-day free trial has ended", without the service being asked. Extension 0.8.5 (on the Chrome Web Store as of 8 October 2026) keeps no count: it asks the service, which knows your plan.

  1. Check the version: chrome://extensions (Edge: edge://extensions) → RepoGates. If it is older than 0.8.5, turn on Developer mode and press Update, or wait for the browser to update it.
  2. Open RepoGates' Options page. The box at the top should read Unlimited repository checks. If it reads "Not signed in", sign in at your account page and press Activate extension.
  3. Still refused on 0.8.5 with a paid plan? Write to support@repogates.com with the date and the repository; the audit log (Options → Audit log) shows what was decided.

"It says NOT CHECKED — what exactly does that mean?"

Precisely one of these, and the page says which:

  • Trial used up or expired — 10 repositories or 14 days, whichever came first.
  • Sign in — the service requires an account before it assesses anything cold.
  • Device limit — the account is signed in on more devices than the plan allows.

In every NOT CHECKED case: the repository was not examined, the badge is not a verdict, known malware is still blocked, and whatever you choose is recorded.

"Download stopped: NOT IDENTIFIED"

Since extension 0.8.6. The link is on github.com, gitlab.com or huggingface.co and has the shape of a download, but nothing in it says which repository or project it belongs to, so RepoGates could not check it. It is not a verdict about the file. The usual case is a gitlab.com download link that names its project only by number, opened from another site. With Fail closed (the recommended setting) a download that cannot be checked is stopped; with Fail open it goes through unchecked.

  1. Open the project's own page and download from there. On the project page RepoGates knows which project the link belongs to, and checks it.
  2. If your policy allows overrides, proceed from the page. It is recorded in the audit log and applies to this download only: with no repository named, there is nothing to remember it for.
  3. If you think the link names its repository plainly, send it to support@repogates.com.

"RepoGates blocked something I trust"

  1. Read the findings on the decision page — the check names say exactly what fired and why.
  2. If you accept the risk and overrides are enabled, override — it is recorded and remembered for the session.
  3. For a repository you use regularly, add it to the allowlist (Options → Protection). Note the one exception: confirmed campaign-blocklist entries block even when allowlisted.
  4. Tell us: support@repogates.com with the owner/repo and the check names from the page or the audit log. False positives are measured and published — reports genuinely change the thresholds.

"The score badge / board disappeared"

The GitHub-page overlay has a server-side kill-switch for the day GitHub changes its markup, so a broken layout is never shown. When it is off, enforcement is completely unaffected — the overlay is display, the gate is the product.