A deterministic CI gate for AI-written code: on every GitHub pull request it decides pass or block before the code reaches main. No score, no debate.

Does my code leave my CI?

No — 0 egress. Extraction stays on your GitHub Actions runner; only a verdict leaves. The code doesn't travel (physical split).

How much does it cost?

Advisory (scan without blocking) is free forever on all your repos. Blocking mode is $24 per repo per month, down to $11 at volume.

Is there a free trial?

Yes: 14 days free, up to 5 repos, no credit card. After the trial you keep the repos you want or fall back to free advisory.

What does the firewall detect?

124 gate classes across 6 categories — injection, crypto, infra, auth, access, supply-chain — including the #1 cross-tenant leak: a query with no org filter. Calibrated to 0 false positives on 5,000+ real repos.

slopGrade

CI gate · AI-written code

AI writes your code.
slopGrade decides: it passes or it blocks.

A deterministic gate on every PR. The slop and cross-tenant leaks it catches never reach main — no score, no debate.

Start — 14 days free See the gate run ↓

Block for real, free — 14 days, up to 5 repos, no card.

No card · expires on its own, never a surprise bill · falls back to free advisory after.

0 egresskeyless OIDCinstalls in 2 min

PR #128acme/billing-apigate live

Pushed · the gate reads the diff

export async function listInvoices(orgId){- return db.from('invoices').select('*') }

!Blockedquery with no org filter · cross-tenant leak

fix pushed ↓

Re-pushed · the gate re-runs

export async function listInvoices(orgId){+ return db.from('invoices').select('*').eq('org_id', orgId) }

✓Passesorg_id filter added · ready to merge

Merge disabled while the slop check is red

Read-only on your diffs Writes only a check status 0 egress — code never leaves your runnergate live

01The problem

Your team merges code no human wrote.

AI agents open PRs faster than review can keep up. Slop slips through, queries forget the org filter, a key leaks into a log. At volume, human review catches nothing — you need a deterministic gate, not an opinion.

02How it works

One loop: detect → block → verify

The gate lives in your GitHub Actions CI. It reads each PR's diff, decides, and writes its verdict as a required check. No code leaves your runner.

detectblockverify

01 · install

Copy the snippet

One GitHub Actions workflow pasted into your repo. Keyless OIDC — nothing to store.

- uses: maxor-tech/slopgrade-firewall@v0.7.0

02 · detect

The PR opens

The gate reads the diff on the runner and classifies it against {gates} classes of slop and tenant leaks.

$ slop scan --diff origin/main…HEAD

03 · block

Pass / block verdict

One required check, true or false. Red → merge is disabled by the branch ruleset.

slop · blocked → merge disabled

04 · verify

The fix goes green

The agent fixes, re-pushes, the gate re-runs. Green → the PR is mergeable again.

slop · pass → ready to merge

no riskStart in advisory on all your repos — it flags reds without blocking anything. Watch what it catches on your real PRs, then switch to blocking when you trust the gate.

03The firewall

124 classes of gate. 5 layers. 0 false positives.

The cross-tenant leak — a query with no org filter — is the class CodeQL and human review miss, and it's our #1. The moat isn't the mechanism: it's the curated, turnkey rulepack, calibrated to zero false positives on 5,000+ real repos before every release. You turn it on; you don't write it.

Classes by category · live catalog

Injection61

Crypto26

Auth15

Infra15

Access5

Supply-chain2

Tenant isolation

Every org-scoped query must carry its filter. The #1 cross-tenant leak in prod, caught before merge.

Secrets & injection

Hardcoded keys, SQL/command/XXE/SSRF, deserialization — the bulk of the catalog.

Crypto & auth

Weak algorithms, short keys, RSA padding, reflected CORS, missing access control.

Deterministic slop

Invented numbers, dead guards, hand-rolled native controls — the formula, never an LLM.

Physical split, 0 egress

Extraction stays on your runner; only a verdict leaves. The code doesn't travel.

04The proof

124

gate classes

Derived from the live catalog — 6 categories, growing weekly.

5,000+

calibration repos

Each class hits 0 false positives on the corpus before release.

0 egress

code doesn't leave

Split IP: extraction on your runner, classifier closed server-side.

2 min

to install

Keyless OIDC, one workflow snippet, protects main.

05Pricing

Free advisory forever. Blocking at $24 per repo.

You pay for what you protect, not per head. A dormant repo costs $0 — and the more you protect, the less each repo costs: $24 for the first, as low as $11 at volume.

Free · advisory

$0 / forever

See every leak we flag — free, on all your repos.

✓ All 11 classes in advisory on every repo
✓ You see the reds — you can't block them yet
✓ Climate, recent runs, leak discovery

Start in advisory

The product

14 days · 5 repos · no card

Firewall · blocking

$24 / repo / month

The gate actually blocks the merge. Protect your whole org at once.

✓ The gate blocks the merge on a red (branch ruleset)
✓ Tenant isolation enforced, not just flagged
✓ Down to $11/repo at volume
✓ 14 days free, up to 5 repos, no card

After 14 days: keep the repos you want at $24 — or fall back to free advisory. No interruption, no surprise bill.

Start — 14 days free

One cross-tenant leak caught = years of subscription.

The hero bug — a query with no org filter in prod — is a breach notification. The gate stops it for $24.

See the full volume curve →

Put a gate between the AI and your main branch.

Create an account, paste the snippet, protect your first repo in two minutes. 14 days free, up to 5 repos, no card.

Start — 14 days free How the firewall decides