compare
Burrito vs Digger
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Burrito | Digger |
|---|---|---|
| Language | Go | Go |
| Licence | Apache-2.0 | MIT |
| Stars | 757 | 5k |
| Latest | v0.14.1 | v0.6.152 |
| Last push | 2026-10-05 | 2026-09-30 |
| Release cadence | about 40 days between releases | about 9 days between releases |
| Active contributors | 9 commit authors on the default branch in the last 90 days | 3 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace HCP Terraform. Alternatives to HCP Terraform →
PartialBurritoRuns Terraform and OpenTofu plans, applies and drift detection from a Kubernetes operator, with no state hosting.
PartialDiggerRuns plan and apply inside your existing CI from pull requests, with locks and policies, without remote workspaces.
Burrito
Digger
- v0.6.1522026-09-30fix: adjust GitHub check run char limit considering the MD terraform text wrapper
- vLatest2026-09-15Rolling release tracking develop.
- v0.6.1512026-09-13fix: bump all node20 actions in action.yml to Node 24 versions
- v0.6.1502026-09-10feat: make git clone timeout configurable via digger.yml
- v0.6.1492026-08-11fix: paginate ListReviews in GetApprovals so approvals beyond 30 comments
Burrito
✓ signed The latest release, v0.14.1, carries a signature GitHub verified.
Loading the security report
Digger
✓ signed The latest release, v0.6.152, carries a signature GitHub verified.
Loading the security report