Inspect Terraform and OpenTofu configuration with a real HCL parser — sensitive defaults, unpinned providers, local state and variables with no type constraint.
Waiting for Terraform configuration
Nothing is run, no state is read and no cloud account is contacted.
The findings appear here
A sensitive variable with a committed default, an unpinned provider, a variable with no type constraint, and local state where a remote backend belongs.
This reads the structure of your configuration with a real HCL parser. Expressions are not evaluated and no provider schema was consulted, so it cannot tell you an argument name is wrong or a value is invalid — only `terraform validate` against the real providers can. Nothing here ran Terraform, read state, or contacted a cloud account.
Terraform Configuration Inspector runs entirely on your device — credential-shaped values are reported by name and never read, and no state file or cloud account is touched.
You’re on the Free plan. Compare plans
This parses HCL rather than pretending JSON is close enough. Heredocs, `${}` interpolation containing nested braces and quoted strings, expressions that span lines inside brackets, all three comment syntaxes, and a `#` that means nothing special inside a string — every one of those breaks a line-by-line reader, usually by mangling a policy document.
The difference shows up on real configuration: an IAM policy in a heredoc is one attribute, not forty lines of mystery, and the block tree reflects what Terraform will actually see.
Credentials are matched on the name and never on the value. A variable or attribute called `password`, `secret_key`, `client_secret` and so on is reported by name, and the finding says the value is not shown on purpose. A Terraform configuration pasted into a tool is exactly the kind of file with a real key sitting in it.
The finding most worth having is a sensitive variable with a default. The default is committed, and `sensitive = true` only redacts it from plan output — it does nothing about the file it is written in, and nothing about the state file, which stores it in clear. Marking something sensitive is not the same as protecting it.
What this cannot do: expressions are not evaluated and no provider schema was consulted, so it cannot tell you an argument name is wrong or a value is invalid. Only `terraform validate` against the real providers can. Nothing here ran Terraform, read state, or contacted a cloud account.
No, and this is the point worth internalising. It redacts the value from plan and apply output. The default is still in the file you committed, and the resolved value is still in the state file in clear text. If something must not be committed, it must not have a default.
No. `terraform validate` loads your provider schemas and checks that every argument exists and every value has the right type. This has no schema at all, so it will happily accept `aws_s3_buckit`. The two find different classes of problem and both are worth running.
Yes — that is one of the reasons it tokenises rather than matching lines. A heredoc body is one attribute value, left exactly as written, so the structure around it reads correctly instead of dissolving into forty unexplained lines.
Neither. It reads the configuration text you paste and nothing else. No state, no credentials, no provider, no cloud account, and nothing leaves your browser.