The download gate and overrides

The decision page and overrides

When a download is stopped, the extension cancels it — Chrome discards the partial temporary file — and opens a page showing:

• the badge and the repository name (owner/repo);
• the findings that drove the decision, sorted by severity, each with its check name and detail;
• an AI-provenance note when a known AI surface led you there: agent-recommended repositories are a known malware seeding channel (AgentBaiting), and an agent recommendation is not a trust signal;
• the actions: Proceed with download (warnings), Override and download anyway (blocks, only when your policy allows overrides), Back to GitHub, and Close.

How much to trust it

Pressing proceed does not download anything yet. It asks a second question — how much do you trust this repository?

• Allow only this time — the grant lasts for the current browser session, for that one repository. Then the gate applies again.
• Permanently allow this repository — saved to your account, so it applies in every browser you sign in to. Manage or remove these under Allowed repositories on your account page.

Neither ever overrides a repository later confirmed malicious: a permanent allow is a convenience, and the campaign blocklist is checked first. If you try to permanently allow one that is on that list, the request is refused and says so, rather than saving an entry that would be quietly ignored.

Proceeding past a warning is recorded as proceeded; overriding a block as overridden; an allowed repository as allowlisted — all in the audit log, with the checks that fired. An override is never available for the quota, sign-in or unreachable screens' assessments — there is nothing to override, because nothing was judged; on those screens the proceed button simply continues an unassessed download, and says so.