SlopGradeby Maxor Global LLC
Sign inStart free
Security & data flow

What leaves your CI. What never does.

slopGrade is a GitHub Action that runs in your runner. By default your code never leaves it — only a structural fingerprint does. Here is exactly what is sent, where it goes, and how to check it yourself.

Three modes, three answers

It depends only on what you turn on.

Default · every repo

Fingerprint only

Sent
File paths and {file, line, kind} per finding.
Never sent
Your code, file contents, secret values.
Where
app.slopgrade.ai, proven by a GitHub OIDC token.
Opt-in · paid repos

Deep scan

Sent
The source of at most 40 files / 2M characters — only files that hold a dangerous sink.
Kept
Nothing of the code — forwarded to the engine, then dropped. Only file:line, the CWE and a one-line evidence stay.
Default
Off. Advisory when on ; blocking only if you choose.
Enterprise

Self-hosted

Sent
Nothing. The engine runs in your infrastructure, air-gapped.
For
Code that must never leave (regulated, air-gapped networks).
What a fingerprint looks like

A location and a kind. Never the line itself.

// one finding, as posted by the default run
{ "file": "src/export.ts", "hits": [{ "line": 14, "kind": "node-exec" }] }
no source codeno file contentsno secret valuesno stored token
Verify it yourself

Don't trust us — check the payload.

01

Print the payload

node isolation-gate.mjs --print-payload prints exactly what would be posted, then exits without contacting the server.

02

Pin the commit

The client is MIT open source with zero npm dependencies. Pin the commit SHA — a tag can move, a SHA cannot.

03

Your token, your repo

The PR comments and the Security-tab upload use your own GITHUB_TOKEN, to your own repo. Those findings never reach us.

Identity & integrity

No stored secret. A fixed endpoint. Fail-open by default.

How does slopGrade know which repo is calling?

A short-lived, GitHub-signed OIDC token, audience-bound to our origin. There is no API key to store or leak.

Can a workflow redirect the payload elsewhere?

No. The endpoint is fixed ; a custom origin is refused unless you explicitly allow it for your own self-hosted server.

What runs on my runner for paid repos?

Closed-source extractors for the rest of the catalog, downloaded at run time, size-bounded and sha256-checked. Their output passes a second egress filter that drops any source-bearing field.

What if slopGrade is down?

The build never breaks : every call is bounded and fails open. Set strict: "true" if you'd rather fail closed.

Report a vulnerability

Found something? Tell us first.

Write to hello@slopgrade.ai — our /.well-known/security.txt lists the same contact.