Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

I got tired of production incidents caused by bad config, so I built a scanner

Description and use

StackGuard scans infrastructure configs and provides a production‑readiness score, enabling teams to catch misconfigurations in Kubernetes, Terraform, Dockerfiles, and more before deployment.

Problem

Production incidents were repeatedly caused by overlooked configuration mistakes in Kubernetes, Terraform, Dockerfiles, and other infra files, leading to outages and security risks.

Outcome

StackGuard reduced the need for multiple tools, provided a single numeric score to track infra health, and enabled CI gating and PR annotations, helping teams catch misconfigurations before deployment.

Workflow

  • Point StackGuard at a repository root (e.g., stackguard scan .), Configure minimum score and failure conditions (e.g., --min-score 80 --fail-on error), Generate SARIF output for PR annotations, and Upload SARIF to GitHub Actions for inline review.
  • The tool automatically discovers file types, parses them into resource trees, evaluates compiled rules, and reports findings in console, JSON, SARIF, HTML, or CSV formats.

Evidence

Our API pods were getting OOMKilled in a loop. Users were seeing 502s. The Slack channel was lighting up.

Source

Adding resources.limits.memory: 512Mi to the deployment manifest. The incident took four hours.

Source

I looked at what was out there. There are great tools, don't get me wrong. But here's what I kept running into: Scattered coverage. No single number.

Source

StackGuard is a single Go binary that scans your infrastructure config, Dockerfiles, Compose files, Kubernetes manifests, Helm charts, Terraform, GitHub Actions, Jenkinsfiles, Ansible playbooks, and nginx configs against a set of rules and gives you a production-readiness score out of 100.

Source

A score, not a wall of text. Every error costs 10 points, every warning costs 3, every info costs 1. Your score is 100 minus the deductions.

Source

Rules are YAML, not code. Drop a YAML file in a directory and it loads on the next scan.

Source

  • Record date: 2026-11-02T05:29:09.884Z