All 27 Dependencies
Every package infracost depends on, ranked by repo health score.
Infracost is a command-line tool that turns Terraform, Terragrunt, CloudFormation, and AWS CDK code into a concrete monthly dollar estimate before anything gets applied. Instead of waiting for a cloud bill at the end of the month, engineers run `infracost breakdown` against a project directory or plan file and get a resource-by-resource cost table, or run `infracost diff` in CI to see exactly how much a pull request will change spend. It is written in Go and distributed as a single static binary, installable via Homebrew, Chocolatey, or a shell script, with no cloud credentials required for the common case.
Under the hood, Infracost implements its own HCL parser and dependency graph evaluator (`internal/hcl`) that resolves Terraform modules, variables, and outputs statically — without shelling out to `terraform plan` or touching real cloud accounts — falling back to invoking the Terraform CLI only when explicitly requested via `--terraform-force-cli`. CloudFormation and synthesized AWS CDK templates are parsed with the `awslabs/goformation` library. Resolved resources are matched against per-cloud-provider cost models (over 1,100 resource types across AWS, Azure, and Google Cloud, in `internal/resources`) and priced through Infracost's hosted GraphQL Cloud Pricing API, with bundled `infracost-usage-defaults.*.yml` files supplying realistic default usage for consumption-priced resources like S3, Lambda, and DynamoDB that would otherwise show $0.
The CLI is the core of a wider toolkit: a Language Server powers cost-lens extensions for VS Code, JetBrains IDEs, Neovim, and Zed; a separate `agent-skills` package plugs cost and FinOps policy checks into Claude Code, Cursor, and other AI coding agents as they generate infrastructure code; and `infracost comment` posts cost-diff comments directly on GitHub, GitLab, Bitbucket, and Azure Repos pull requests. Infracost Cloud, a hosted SaaS dashboard, layers team-wide tagging policies, spend guardrails, and cross-project visibility on top of the same engine, but the CLI and estimation engine themselves remain fully open source under Apache 2.0.
As of the 2.0 restructuring, this repository is described by the maintainers as the ecosystem's front door — the actual estimation engine (HCL parsing, resource pricing, output formatting) still lives here, while editor extensions, the language server, and agent skills have been split into sibling repositories under the same GitHub organization.
