# diggerhq/digger

Digger is an open source IaC orchestration tool. Digger allows you to run IaC in your existing CI pipeline ⚡️

Repository: https://github.com/diggerhq/digger
Canonical: https://ross.abutalabs.com/products/digger
Homepage: https://digger.dev
Language: Go
License: MIT
License Family: permissive
Topics: infrastructure-as-code, terraform, terraformcloud, tacos, github-actions, terraform-aws, terraform-gcp, terraform-github-actions, hacktoberfest
Last push: 2026-08-11T18:59:55+00:00

## Health v2 (maintenance only)
Score: 92/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 97, release rhythm 85, longevity 91
- inputs: {"age_days": 1286, "days_push": 22, "days_rel": 22, "gap_med": 0.0, "n_releases_24m": 275}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 5031, forks 608 (observed 2026-08-28T04:09:08.657914+00:00)

## What it is
Digger (now rebranded OpenTaco) is an open-source Infrastructure-as-Code orchestration tool that runs Terraform plan and apply directly inside your existing CI pipeline, such as GitHub Actions. It provides Atlantis-like PR automation without requiring a separate server, keeping cloud secrets and compute within your own infrastructure.

## Use cases
- run terraform plan and apply from pull request comments
- replace terraform cloud or atlantis with ci-native automation
- avoid sharing aws credentials with a third-party terraform service
- add pr-level locks to prevent terraform race conditions across prs
- detect terraform configuration drift
- enforce opa policies and rbac on terraform changes
- run terragrunt or terraform workspaces in github actions

## When to choose
- you already use GitHub Actions or another CI and want Terraform automation without hosting a separate server
- security policies forbid sharing cloud credentials with external TACOS like Terraform Cloud or Spacelift
- you want Atlantis-like workflows with drift detection, OPA policies, and apply-after-merge
- you want to reduce costs by reusing existing CI compute for Terraform runs

## When to avoid
- you need a fully managed, turnkey Terraform platform with a dedicated web UI and support
- your CI system is not supported or you cannot modify pipeline configuration
- you prefer a long-running server-based workflow like vanilla Atlantis
- you don't use Terraform, OpenTofu, or Terragrunt for infrastructure management

## Facets
- artifact type: cli-tool
- maturity: active
- function: infrastructure-as-code, ci-cd, deployment, workflow-automation, developer-tools
- domain: infrastructure-as-code, cloud-computing, developer-tools
- platform: cli, self-hosted, cloud
- tags: terraform, opentofu, terragrunt, atlantis-alternative, github-actions, terraform-automation, pr-automation, drift-detection, opentaco, devops, automation, github, docker

## Member repositories
- diggerhq/digger (main) score 92

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:08.657914+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:17:27.253978+00:00, confidence not recorded.
  - readme: https://github.com/diggerhq/digger (fetched 2026-08-28T04:09:08.657914+00:00, sha 5166a37eb98e)
  - homepage: https://digger.dev (fetched 2026-08-29T08:57:59.729963+00:00, sha c6c41593d8d7)
- Data as of 2026-08-30T08:39:29.467469+00:00.