Catch the apply that destroys your cloud — and the dependency that poisons it.
bumper reads your Terraform plans andyour lockfiles, and blocks the two changes you can't take back: an apply that would expose or destroy your AWS, GCP, or Azure account, and an install that pulls in a known-vulnerable or malicious package — before either one runs. A single static Go binary. The verdict is 100% deterministic.
Catch the apply before it destroys production.
A real bumper --explain plan.json run on a plan that opens and destroys production. Every finding gets a plain-English line and a one-line fix.
Catch the package before it lands in your tree.
A real bumper deps run over a lockfile — known CVEs and known-malicious packages, checked against the hosted Advisor. Only package coordinates leave your machine, never your code.
Your AI agent can no longer silently
destroy your cloud — or install malware.
Run bumper initinside Claude Code, Augment, or Gemini CLI and it installs tool-layer hooks. The agent can't run an unverified terraform apply, and can't install a known-malicious package — both are blocked before they run, not flagged after. It also installs agent skills — SKILL.md playbooks that teach the agent to reach for the gate, the dependency scan, and the Advisor on its own.
Above, the Terraform apply gate in action. The dependency gate works the same way at the tool layer: a known-malicious install is a hard block before it runs, while a vulnerable package is surfaced for the agent to upgrade. Critical and destructive findings always wait for an explicit human decision; lower severities stay overridable, so the gate stays useful instead of becoming noise. bumper gates; it doesn't hold you hostage.
Hooks are the push; the skills are the pull. Installed as the open, cross-agent SKILL.md standard, they give the agent the playbook for each surface — so it scans the plan before applying, triages a flagged dependency, and looks a CVE up in the Advisor without being told.
gating-terraform-plans · triaging-vulnerable-dependencies · querying-the-bumper-advisor. The same files feed every channel.Three things most tools miss.
It reads the transition, not the result.
Most IaC scanners check the config you'd end up with. bumper reads the plan's create / delete / replacemoves — so it catches “this apply will destroy your production database,” not just “this bucket is misconfigured.”
It blocks malice, not just bugs.
Dependency scanning flags known-vulnerable versions and known-malicious packages — typosquats and backdoors that run at install time. The supply-chain attack gets denied before it runs, not reported after the damage.
It enforces — and stands alone.
verify binds a passing scan to the plan by sha256 and guardblocks an unverified apply; a malicious install is denied in the agent loop. And the verdict never depends on a model — it's 100% deterministic, so you can safely block a merge on it.
A knowledge MCP for rules, CVEs and malware.
bumper's local scanner is offline and deterministic — that never changes. The Advisor is the optional hosted half: a single Model Context Protocol server (and matching REST API) your AI tools can query for IaC remediation guidance across AWS, GCP and Azure, CVE lookups, and known-malware checks.
Everything bumper knows, hosted free
Point your editor or agent at the Advisor and it reaches the whole corpus — 2,700+ IaC rules & advisories(Trivy, Checkov, KICS, Prowler + bumper's enforced set), 178k+ CVEs across 3.4M affected versions, and 226k+ known-malicious packages. Hosted on our box, free to use, no account.
A lookup key is all that leaves
The only thing that ever leaves your machine is a lookup key — a search phrase, or for the dependency guardrail, package coordinates (ecosystem · name · version). Your plan, state, lockfile and code never do. scan, verify, guard and deps all parse locally; only the lookup is remote.
Always current
The mirror refreshes server-side every day from OSV, Trivy, Checkov, KICS and Prowler — so CVE, malware and rule guidance keep improving without you shipping a new binary or pulling a multi-gigabyte database.
Hosted by default — or run your own
Nothing to install: point your client at the hosted Advisor over MCP and REST — search_rules for IaC, lookup_cve and check_malware for dependencies, plus semantic search across all three; bumper init wires it in one line. The whole service is open source (Apache-2.0), so you can self-host it and keep even package coordinates in-house.
# one line wires the hosted Advisor into any MCP client { "mcpServers": { "bumper-advisor": { "type": "http", "url": "https://advisor.bumper.sh/mcp" } } } # or let bumper write it for you: $ bumper init --advisor
Drop it into the pull request.
Two composite Actions, one signed binary — gate your Terraform plans and your lockfiles on every PR, reported where developers already look.
Get it on the GitHub Marketplace →SARIF to the Security tab
Both gates upload SARIF, so plan findings andvulnerable/malicious packages appear inline in GitHub's Security tab.
One sticky PR comment
A single comment, updated in place on every push. No thread spam, no walls of duplicate output.
Fails on high+ — malware always
Exits non-zero on a high or critical finding so the check blocks the merge — and a known-malicious package always fails the job, no matter the threshold.
# one gate for infra + dependencies, on every PR name: bumper on: [pull_request] jobs: infra: # terraform plan safety gate runs-on: ubuntu-latest steps: - uses: gnana997/bumper@v1 with: { plan-json: plan.json, fail-severity: high } deps: # dependency CVE + malware gate runs-on: ubuntu-latest steps: - uses: gnana997/bumper/deps@v1 with: { fail-severity: high } # malware always fails