stackrox/kube-linter

KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 19th, 2026
Created on August 13th, 2020
Open Issues & Pull Requests: 85 (+0)
GitHub issues: Enabled
Number of forks: 274
Total Stargazers: 3,508 (+0)
Total Subscribers: 35 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 0
Closed in 7 days: 5
Avg open age: 660 days
Stale 30+ days: 26
Stale 90+ days: 21

Recent activity

Opened in 7 days: 0
Closed in 7 days: 5
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (15)
  • good first issue (10)
  • new-check (10)
  • help wanted (5)
  • hacktoberfest (4)
  • needs design (4)
  • bug (3)
  • decision pending (2)

Detailed Description

KubeLinter is a static analysis tool that checks Kubernetes YAML files, Helm charts, and Kustomize manifests against best practices focused on production readiness and security.

The tool addresses the problem of ensuring Kubernetes configurations follow organizational policies and security standards before deployment. Common checks include verifying containers run as non-root users, enforcing least privilege principles, and ensuring sensitive data is stored only in secrets. Organizations can enable or disable built-in checks and create custom checks tailored to their specific policies.

KubeLinter suits teams that want to catch configuration issues early in development and enforce consistent standards across Kubernetes deployments. It works well for projects using Helm charts or Kustomize alongside raw YAML, and integrates into CI/CD pipelines through its command-line interface and container images. The tool is particularly valuable for security-conscious organizations that need to validate configurations against multiple best practices simultaneously.

The project maintains multiple testing layers including Go unit tests, end-to-end integration tests, and bats-core integration tests, all of which are expected to pass. Container images are signed with cosign and can be verified using the project's public key or keyless signature verification. The project provides installation options across multiple package managers and platforms, including Go, Homebrew, nix-shell, and Docker, with binaries available from releases.