Install GitHub agentBook a demo

Plumber: Leaking CI/CD pipelines kill your company. Plumber prevents it.

CI/CD security posture management

Leaking CI/CD pipelines kill your company. Plumber prevents it.

See on GitHubBook a demo

AI now writes your pipelines, and nobody reviews them. Plumber checks every pipeline before it runs, grades it from A to E, and opens the pull request that fixes what it finds.

Get your Plumber Score

Or run it yourself:Plumber Scan

Coverage and grading overview
  • A–EOne grade for every pipeline
  • GitHub + GitLabSame checks, same score
  • Open sourceVerify any grade yourself

Why it's happening

AI writes your pipelines.
Attackers walk right in.

Developers now prompt their pipelines instead of writing them. The AI copies the insecure defaults it learned from millions of public repositories. The pipeline still turns green, because green means the build worked, not that it is safe.

  • 2xAI-assisted commits leak secrets twice as oftenGitGuardian, State of Secrets Sprawl 2026
  • 48.8%of organizations use AI for at least one CI/CD taskGitGuardian, State of Secrets Sprawl 2026

Your pipeline is green. It's also leaking.

.github/workflows/deploy.yml3 issues found
  1. 1name: Deploy
  2. 2on: [push]
  3. 3jobs:
  4. 4 deploy:
  5. 5 runs-on: ubuntu-latest
  6. 6 permissions: write-all1
  7. 7 env:
  8. 8 AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}2
  9. 9 steps:
  10. 10 - uses: actions/checkout@v4
  11. 11 - name: Get changed files
  12. 12 uses: tj-actions/changed-files@v453
  13. 13 - run: ./deploy.sh

The numbers behind the blind spot

Attackers moved
to the pipeline.

A pipeline holds the keys to your code, your cloud and your customer data. It has more access than most engineers and gets reviewed less than any other part of the codebase. Attackers know it.

Incident log

DateFigureWhat happenedSource
Oct 202652%of 104,500 public projects had at least one CI/CD attack pattern.Plumber Radar Scan
Nov 202625,000+public GitHub repos filled with stolen credentials within hours, as the Shai-Hulud 2.0 worm hit Zapier, PostHog and Postman.Wiz Research
Nov 202659%of the machines it compromised were CI/CD runners, not laptops.GitGuardian, State of Secrets Sprawl 2026
Mar 202523,000+repositories ran a hijacked GitHub Action that dumped their CI secrets into public build logs. One unpinned line of YAML was enough.tj-actions/changed-files, GHSA-mrrh-fwg8-r2c3
Dec 2024260,000daily downloads of Ultralytics, a top AI library, when attackers slipped a crypto miner into its release through a branch name its GitHub Actions workflow never checked.BleepingComputer and Wiz

How it works

Plumber finds the leak
and brings the fix.

One loop, run on every pipeline, every time it changes.

  1. 01MapDiscover every pipeline across all your repos, on GitHub and GitLab.
  2. 02FindSurface unpinned third-party actions, tokens with too much access, and missing branch protection.
  3. 03FixAI writes the fix. Plumber's rule-based engine checks every change before your team sees it, then opens the pull request.
  4. 04GradeEvery pipeline gets a Plumber Score from A to E. Set a threshold and block any merge below it.

Nothing merges without your review. Every fix arrives as a pull request your team can read, test and reject.

Choose your path

One product.
Two ways to use it.

Same engine, same score. Pick the entry point that fits how you work.

01

For Developers

Open source. Runs in your terminal, a GitHub Action or GitLab CI. Scan your pipeline and fix issues before they ship. No setup, no account.

Install the GitHub AgentInstall the CLI
02

For Organizations

Continuous CI/CD security posture across every repo and every team. One dashboard, audit-ready reporting, and an AI agent that fixes what it finds.

Securing one pipeline by hand takes about an hour a month. For 500 pipelines, that's $600k per year.
Book a demo

Trusted by the community, built for scale

Don't take our word for it.
Check the grade.

Every check Plumber runs is open source. Run it on your own pipeline and you'll get the same grade we do.

View on GitHubJoin the Discord
100+
open-source projects graded A or B
25,000+
open-source downloads
16,644
public projects graded
250k+
leaks found
  • We needed visibility first. Standardization came next. Now our CI/CD pipelines are clear, consistent, and easier to maintain.
    Lucas Delcroix-EustacheCTO at Libération
  • Numspot requires continuous monitoring of its CI/CD pipeline compliance. Auditability is a critical focus to ensure that pipeline security processes do not deviate over time.
    Olivier LAVAUXCISO at Numspot
  • Numspot's sovereign platform is intentionally designed to incorporate security and compliance as fundamental elements, embedded into every pipeline from day one, providing the level of security and compliance needed to navigate qualifications and certifications with peace of mind.
    Steve ALBERTHead of Operations at Numspot
  • We are both a consulting firm and a software publisher. With Plumber, we empower our clients to achieve Security by Design while enabling our developers to build compliant pipelines effortlessly. It transforms compliance from a manual burden into an automated, auditable process.
    Nicolas PETROUSSENKOCOO at Point Base
  • Compliance is not just about the product. We must also prove that the way we build and deliver it is secure.
    Yann HILLEREAUIT Manager at FDI Access

FAQ

Questions

Plumber is CI/CD security posture management that fixes what it finds. It checks how every pipeline is built, grades it from A to E, and sends the fix as a pull request your team reviews and merges. It runs on GitHub Actions and GitLab CI/CD, and the engine is open source on GitHub.
Runtime tools watch what your application does once it is deployed. Plumber looks at the stage before that: how the pipeline itself is built. It checks the workflow and CI configuration, the tokens and permissions a job can use, the third-party actions it pulls in and the branch protection around it, so a leak is caught before anything ships.
Every fix is checked by a deterministic, rule-based engine before your team sees it, and it always arrives as a pull request. Nothing is applied to your repository on its own. You can read the diff, run your tests, and reject it. The same input produces the same fix, so what the agent changed and why stays auditable.
Yes. Plumber runs the same checks on GitHub Actions workflows and GitLab CI/CD pipelines and produces the same A to E grade, so teams that use both get one comparable score. The CLI runs locally or in CI, as a GitHub Action or a GitLab CI component.
The Plumber Score is a single A to E grade for the security posture of a pipeline. Read it like a credit rating: it turns dozens of technical checks into one letter that everyone on the team understands, so you can track CI/CD security over time, set a threshold, and block merges that fall below it.
The open-source CLI needs nothing beyond the repository it scans: it reads the pipeline configuration and reports. The platform needs read access to your organization to discover pipelines and project settings, and write access only when you want it to open the pull requests that carry the fixes.
The CLI is open source and free, with no account required. The platform is free for up to 10 projects and includes continuous monitoring, history and the AI agent fixes. Larger organizations can book a demo to discuss unlimited projects and dedicated support.

Let's look at your pipelines

Find the leak
before an attacker does.

We'll scan your pipelines, show you their Plumber Score and walk your team through the fixes.