diggerhq/digger

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Added to GitGenius on September 13th, 2026
Created on February 24th, 2023
Open Issues & Pull Requests: 485 (+0)
GitHub issues: Enabled
Number of forks: 611
Total Stargazers: 5,043 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 99.2 days
90th percentile: 358.0 days
Tracked items: 156

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "user-reported" is answered fastest, typically in about 7 days, while "documentation" waits about 6 months. 76% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 18% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 198
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 494 days
Stale 30+ days: 193
Stale 90+ days: 170

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 3

Top labels

  • opentaco (45)
  • documentation (28)
  • user-reported (14)
  • good first issue (12)
  • enhancement (7)
  • question (4)
  • bug (3)
  • need for backend (3)

Detailed Description

Digger is an open source infrastructure-as-code orchestration tool that runs Terraform natively within your existing CI pipeline instead of requiring a separate specialized system.

Terraform CI/CD introduces complexity around secret management, compute scaling, and coordination across pull requests. Digger solves this by embedding orchestration directly into your CI environment. The tool consists of a CLI component that executes within your CI jobs and calls Terraform with appropriate arguments, plus a minimal backend orchestrator that triggers CI jobs in response to events like PR comments. State locks, plan caching, and coordination metadata are stored in your cloud account rather than a third-party service, keeping sensitive data within your infrastructure boundary.

Teams should adopt Digger if they want to consolidate their CI/CD stack and avoid paying for separate compute resources dedicated to infrastructure automation. It suits organizations already invested in GitHub Actions or similar CI systems who prefer not to maintain an additional server or share cloud credentials with external platforms. Compared to Atlantis, Digger requires no server hosting, runs jobs within your CI's compute environment for better scalability, and includes drift detection and OPA-based RBAC. Against Terraform Cloud and similar specialized systems, the tool offers open source code with self-hosting options, unlimited runs regardless of tier, execution within your CI rather than third-party infrastructure, and no credential sharing with external services.

The project maintains active development with regular updates to documentation and feature additions. The codebase shows ongoing refinement of core functionality including support for Terragrunt, multiple Terraform versions, and static analysis integration. Community engagement is facilitated through documented channels including a Slack community and scheduled demos. The project has undergone significant evolution in scope and positioning, expanding beyond its original focus on Terraform PR automation to address broader production infrastructure needs.