Docs / CI/CD integration
Stop a deploy when the site still has open high or critical security findings, so a known vulnerability never ships unnoticed.
Early access. The deploy gate needs a long-lived API key for your CI system, and self-serve API keys are still being added to the dashboard. If you'd like to use the gate now, contact us and we'll set it up with you.
| Exit code | Meaning | Pipeline |
|---|---|---|
| 0 | No open findings at or above the threshold | Continues |
| 1 | Open findings at or above the threshold | Stops |
| 2 | The check itself couldn't run (network or credentials) | Stops, with an error rather than a security failure |
A broken check is reported separately on purpose, so "couldn't check" never looks the same as "all clear".
| Setting | What it is |
|---|---|
| Drubix URL | https://app.drubix.com |
| Site ID | The ID of the site to check. We give you this during setup. |
| Fail on severity | critical, high (default), moderate or low |
| API key | Provided during early access, and later from Account settings. Store it as a secret in your CI system. |
The check is a plain Node.js script with no extra dependencies, so it runs in GitHub Actions, GitLab CI, Bitbucket Pipelines, CircleCI, Jenkins or anything else that can run node. We'll send the script and a ready-made GitHub Actions workflow when we set up your access.
You get the same protection without the gate: