An open-source tool that combines tflint, tfsec, infracost, and inframap to validate Terraform Infrastructure-as-Code.
ValidIaC is an open-source validation tool for Terraform Infrastructure-as-Code that integrates multiple specialized tools into a single interface. It helps developers and DevOps teams ensure their Terraform code follows best practices, is secure, cost-effective, and well-documented. The tool combines linting, security scanning, cost estimation, and infrastructure visualization capabilities.
DevOps engineers, cloud infrastructure teams, and developers who use Terraform to manage cloud resources and want to automate validation, security, and cost oversight in their CI/CD pipelines.
Developers choose ValidIaC because it consolidates four essential IaC validation tools (tflint, tfsec, infracost, inframap) into one easy-to-use package, supports multiple deployment methods (CLI, server, Lambda, Docker), and is entirely open-source and extensible.
ValidIaC combines the best open-source tools to help ensure Infrastructure-as-Code best practices, hygiene & security.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Combines tflint, tfsec, infracost, and inframap into a single tool, simplifying multiple validation steps into one interface as described in the Capabilities section.
Supports CLI, HTTP server, AWS Lambda, and Docker deployments, allowing integration into various workflows from local development to serverless environments.
Avoids vendor lock-in and encourages community contributions, with the README inviting users to add more capabilities or tools.
Covers linting, security, cost estimation, and infrastructure mapping, providing a holistic approach to IaC validation.
Requires installing Graphviz and running 'make deps' and 'make build' commands, adding overhead compared to standalone tools that might have simpler installs.
Upgrading integrated tools involves editing versions in the Makefile and rebuilding, which can be cumbersome and delay updates, as noted in the Development section.
Infracost cost estimation requires an API key, adding configuration steps and potential costs, which isn't needed for core linting or security checks.