kube-score
kube-score.com
- Free plan
- Windows
- macOS
- Linux
- Web
- Self-hosted
What kube-score is
kube-score checks Kubernetes object definitions and suggests changes aimed at application security and resilience. Its checks cover container limits, NetworkPolicy targeting, PodDisruptionBudget, Pod anti-affinity, container probes, security context, and stable APIs. Optional checks can examine resource requests and limits, container ports, and seccomp profile configuration. You can ignore checks or enable optional ones globally or for individual objects.
The tool can run in CI/CD and return exit code 1 for critical errors; warnings can also be set as the exit threshold. Results can be printed in human-readable, JSON, CI, or SARIF formats. The documentation shows workflows with Helm, Kustomize, static YAML files, Docker, and resources from a Kubernetes cluster. It recommends analyzing all applications deployed to the same namespace together for the best results. A browser demo accepts Kubernetes YAML or JSON and runs entirely in the browser, without sending data to a server. Local options include prebuilt macOS, Linux, and Windows binaries, Docker, Homebrew, and Kubernetes Krew. kube-score is free and MIT-licensed; building from source requires Go 1.21 or later.
Who it suits
kube-score suits teams and developers who want static checks for Kubernetes definitions, including in CI/CD workflows. It can also work for people who prefer to paste YAML or JSON into a browser demo that runs locally in the browser.
Good to know, and what to watch
- Checks security and resilience concerns in Kubernetes definitions
- Runs in CI/CD with configurable exit thresholds
- Supports human-readable, JSON, CI, and SARIF output
- Browser demo sends no data to a server
- Free and MIT-licensed
- Best results require all namespace applications as input
- Building from source requires Go 1.21 or later
Plans
Every plan and priceFree and open source
Open source
The Club's review
Overview
kube-score is a free, MIT-licensed static analyzer for Kubernetes object definitions. It suits developers, platform engineers and operators who want configuration checks before deployment or as part of CI/CD, without adopting a paid service. Its broad Kubernetes coverage and adaptable policy make it a strong general-purpose review layer, provided you analyze related applications together rather than treating isolated objects as the whole picture.
The project is open source and available on Linux, macOS, Windows, in self-hosted environments and through a web browser. The online demo accepts YAML or JSON and runs entirely in the browser, according to the maker, so manifests are not sent to a server. That is useful for a quick review or for teams that cannot upload configuration to an external service.
Key features
The checks focus on deployment choices that affect reliability and security. kube-score examines container limits, security contexts, probes, stable API usage, NetworkPolicy targeting, PodDisruptionBudget settings and Pod anti-affinity. Optional checks cover matching resource requests and limits, declared container ports and seccomp profile configuration. This combination catches both obvious omissions and operational details that are easy to miss in a code review.
Policy control is practical rather than all-or-nothing: tests can be ignored globally or for a particular object, while optional tests can be enabled at either level. That lets a team introduce stricter checks incrementally or accommodate a deliberate exception without discarding the rest of the analysis. The trade-off is that maintaining these exceptions becomes part of policy ownership.
kube-score fits several manifest workflows. Documentation demonstrates use with Helm, Kustomize, static YAML files, Docker and resources retrieved from an existing Kubernetes cluster. In CI/CD, critical errors produce exit code 1, and warnings can be chosen as the failure threshold. Human-readable, JSON, CI and SARIF output cover local review, machine processing and pipeline reporting; SARIF is intended to make integration with CI platforms easier.
For the most useful result, the documentation recommends including all applications deployed to the same namespace in the analysis. That scope requirement matters: checking one fragment in isolation can omit relationships the checks are designed to evaluate, so kube-score is less suitable as a complete answer when manifests are routinely reviewed piecemeal.
Pricing
Free and open source — free. The MIT-licensed tool has no paid plans, seat charges, usage quotas or trial period. You can run it locally, in your own infrastructure or in CI without a subscription. Building from source requires Go 1.21 or later; users who do not want to compile it can use prebuilt binaries or the listed package and container options.
Platforms
Prebuilt binaries are provided for Linux, macOS and Windows. Distribution options also include Docker, Homebrew and Kubernetes Krew, while the browser demo provides a web-based route for YAML and JSON checks. Self-hosted execution is appropriate for teams keeping analysis inside their own environment; the browser tool is convenient for an occasional inspection.
Who it's for
kube-score is best for teams standardizing Kubernetes reviews across repositories and deployment stages. Developers gain actionable checks before manifests reach a cluster, while platform and operations teams can enforce failure thresholds in CI/CD and consume structured output. Its MIT license and per-test configuration suit organizations that want to adapt policy rather than accept a vendor-defined rule set.
It is a weaker fit when you need a hosted governance product, centralized reporting or analysis that remains meaningful on isolated snippets. The tool is specifically a static Kubernetes analyzer, so teams looking for broader infrastructure or runtime security coverage should consider a complementary product.
Pros and cons
- Pros: broad checks for security, resilience and API stability in one Kubernetes-focused tool.
- Pros: CI exit thresholds and SARIF, JSON and CI formats support automated gates and downstream reporting.
- Pros: Helm, Kustomize, Docker, static files and cluster resources fit common delivery paths.
- Pros: MIT licensing, no paid tier and multiple installation methods remove procurement and distribution friction.
- Pros: browser execution keeps demo input in the browser rather than sending it to a server.
- Cons: best results require analyzing all applications in a namespace together, which complicates narrowly scoped reviews.
- Cons: optional checks and ignored tests place responsibility on teams to maintain consistent policy.
- Cons: source builds require Go 1.21 or later, adding a toolchain dependency for users who compile it themselves.
Alternatives
Choose Chef InSpec instead when you need a freemium option with a free plan for unlimited-duration, non-production personal or non-commercial workloads and a trial, across API, desktop and self-hosted platforms.
Conftest is a better pick for teams seeking an Apache 2.0 open-source policy-testing tool on Linux, macOS or Windows.
Pick Test Kitchen when its RubyGems, system-package or Cinc/Chef Workstation installation paths and Apache 2.0 license fit your workflow.
kubeconform is an alternative free Kubernetes-focused tool with no paid plans or usage limits stated.
Choose Terratest when an Apache 2.0 open-source project from Gruntwork matches your needs.
CloudSploit suits teams wanting a self-hosted open-source version or a hosted commercial option.
AWS CloudFormation is the natural choice for AWS stack provisioning, though underlying AWS resources carry their own charges.
cfn-lint is preferable for CloudFormation-focused linting on supported Python versions under its MIT-0 license.
For broader discovery, browse Infrastructure Testing Tools and Infrastructure as Code Security Software.
Verdict
Choose kube-score if you need a no-cost, adaptable Kubernetes manifest review that can run locally and fail CI on meaningful findings. Its strongest reason to choose it is the combination of practical checks, configurable policy and pipeline-ready output under an MIT license. Look elsewhere if you need hosted administration, centralized governance or a tool whose analysis does not depend on evaluating namespace-level application context.
The verdict
kube-score covers a broad set of Kubernetes checks and offers several ways to fit analysis into development workflows. For useful results, follow its guidance to analyze the applications in a namespace together.
What the maker publishes
- Analysis input
- The README says results are best when input includes all applications deployed to the same namespace. source
- Browser demo
- The online demo accepts Kubernetes YAML or JSON, and the site states that it runs entirely in the browser without sending data to a server. source
- Browser demo
- The website offers a browser demo for testing kube-score. source
- Browser privacy
- The maker’s website says the browser tool runs entirely in the browser and sends no data to a server. source
- Build requirement
- Building from source requires Go 1.21 or later. source
- Build requirement
- Building from source requires Go 1.21 or later. source
- Checks
- Checks include container limits, NetworkPolicy targeting, PodDisruptionBudget, Pod anti-affinity, container probes, security context, and stable APIs. source
- Checks
- Default checks include container resource settings, network policies, disruption budgets, probes, security contexts, and stable APIs. source
- CI use
- kube-score can run in CI/CD and exits with code 1 for critical errors, with an option to use warnings as the exit threshold. source
- CI use
- kube-score can run in CI/CD and can exit with code 1 when it finds a critical error, or on warnings when configured to do so. source
- Configuration
- Users can ignore tests globally or per object and enable optional tests globally or per object. source
- Distribution
- The maker lists Docker, Homebrew, and Kubernetes Krew as installation options. source
- Install options
- The project provides prebuilt binaries for macOS, Linux, and Windows, plus Docker, Homebrew, and Krew installation options. source
- Integrations
- The README demonstrates use with Helm, Kustomize, static YAML files, existing clusters, and Docker. source
- License
- The project is open source under the MIT license. source
- Open source
- The project is available under the MIT license. source
- Optional checks
- Optional checks include matching resource requests and limits, container ports, and seccomp profile configuration. source
- Output formats
- Supported output formats are human-readable, JSON, CI, and SARIF; SARIF is described as supporting easier integration with CI platforms. source
- Output formats
- The CLI supports human, JSON, CI, and SARIF output formats. source
- Platforms
- The maker lists prebuilt binaries for macOS, Linux, and Windows. source
- Purpose
- kube-score statically analyzes Kubernetes object definitions and recommends ways to improve application security and resilience. source
- Purpose
- kube-score statically analyzes Kubernetes object definitions and recommends improvements to security and resilience. source
- Scope limit
- The documentation recommends analyzing all applications deployed to the same namespace together for the best result. source
- Supported platforms
- Prebuilt binaries are listed for macOS, Linux, and Windows. source
Checked against the maker's pages on 8 Oct 2026.