[PR #4203] Add Terraform Compliance #65697

New Issue

GiteaMirror · 2026-07-15T14:33:12-05:00

GiteaMirror commented

2026-07-15 14:33:12 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4203
Author: @antonbabenko
Created: 5/25/2026
Status: 🔄 Open

Base: main ← Head: add-terraform-compliance

📝 Commits (1)

4bba007 Add Terraform Compliance

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/antonbabenko/awesome-terraform-compliance#readme

Compliance, security, and governance controls for Terraform and OpenTofu infrastructure.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

Fully AI-generated pull requests are not accepted.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 4 other open pull requests. (PRs reviewed: https://github.com/sindresorhus/awesome/pull/4168 , https://github.com/sindresorhus/awesome/pull/4167 , https://github.com/sindresorhus/awesome/pull/4158 , https://github.com/sindresorhus/awesome/pull/4099)
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Is not AI-generated.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
The heading title of your list should be in title case format: # Awesome Name of List.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.
Has a Table of Contents section.
Has an appropriate license.
Has contribution guidelines.
All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI (e.g. GitHub Actions) badge.
You can still use a CI for linting, but the badge has no value in the readme.
Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again. DONE :)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4203 **Author:** [@antonbabenko](https://github.com/antonbabenko) **Created:** 5/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-terraform-compliance` --- ### 📝 Commits (1) - [`4bba007`](https://github.com/sindresorhus/awesome/commit/4bba007f8690034bbf561e4cd806e37eebe04b10) Add Terraform Compliance ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description   https://github.com/antonbabenko/awesome-terraform-compliance#readme Compliance, security, and governance controls for Terraform and OpenTofu infrastructure. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 ## Requirements for your pull request - [x] Fully AI-generated pull requests are not accepted. - [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**. - [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [x] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** (PRs reviewed: https://github.com/sindresorhus/awesome/pull/4168 , https://github.com/sindresorhus/awesome/pull/4167 , https://github.com/sindresorhus/awesome/pull/4158 , https://github.com/sindresorhus/awesome/pull/4099) - [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [x] **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. - [x] Is not AI-generated. - [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new). - [x] The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/). - [x] **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - [x] The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` & `awesome` as [GitHub topics](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics). I encourage you to add more relevant topics. - [x] Not a duplicate. Please search for existing submissions. - [x] Only has awesome items. Awesome lists are curations of the best, not everything. - [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file. - [x] Includes a project logo/illustration whenever possible. - [x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - [x] Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge). - [x] Has a Table of Contents section. - [x] Has an appropriate license. - [x] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines). - [x] All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a `Footnotes` section at the bottom of the readme. The section should not be present in the Table of Contents. - [x] Has consistent formatting and proper spelling/grammar. - [x] Does not use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap). - [x] Does not include a CI (e.g. GitHub Actions) badge.<br>You can still use a CI for linting, but the badge has no value in the readme. - [x] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. **Go to the top and read it again.** DONE :) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-15 14:33:12 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#65697