Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience real numbers from our own analytics — open to see them
–Visitors
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · counted by iTechGuides's own first-party analytics, bots removed, every figure rounded down · how we count

TFLint review

Free#19 of 28 in Infrastructure Testing ToolsBootable USB SoftwareIaC Security Scanners

A focused local linter for Terraform syntax, semantics, and provider-specific rules.

7.4/10Editor score
TFLint7.4 Visit TFLint

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

TFLint is an open-source command-line framework for linting Terraform configurations. It is designed for developers and infrastructure teams maintaining Terraform code across AWS, Azure, Google Cloud, and other provider ecosystems. The linter checks Terraform syntax and semantics, identifies deprecated syntax and unused declarations, and enforces best-practice and naming conventions. Terraform does not need to be installed at runtime for its language parsing capabilities.

Its strongest feature is the plugin-based ruleset architecture. Cloud-provider-specific rules cover AWS, Azure, and Google Cloud, while custom plugins can extend the ruleset for other needs. Teams can enable or suppress rules, inspect directories recursively, and install plugins automatically with tflint --init. Output options include JSON, Checkstyle, JUnit, compact, and SARIF, which fit different reporting and CI workflows. The published integrations include GitHub Actions and Docker, and --fix can automatically address supported issues.

TFLint is a focused choice for static checks inside Terraform development and delivery workflows. It does not cover configuration compliance, provisioning tests, or deployed tests, so teams seeking broader infrastructure validation or runtime verification should consider a tool with those capabilities. Its execution model is local, making it suitable for command-line use, Docker-based workflows, and CI pipelines that teams operate themselves. Choose TFLint when Terraform syntax quality, provider-aware linting, and customizable rules are the priority; look elsewhere when the primary requirement is policy coverage beyond static Terraform analysis.

TFLint pros and cons

  • Where it wins
    • Checks Terraform syntax, semantics, deprecations, and unused declarations
    • Adds AWS, Azure, and Google Cloud rules through plugins
    • Supports recursive inspection, many formats, and automatic fixes
  • Where it doesn't
    • Focuses on static Terraform analysis rather than deployed testing
    • Does not provide configuration compliance or provisioning tests
    • Local execution may require teams to manage CI and runtime integration

TFLint fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.

Last updated · How we research and update