github.com/pdecat/terraform@v0.11.9-beta1/website/docs/registry/modules/verified.html.md (about)

     1  ---
     2  layout: "registry"
     3  page_title: "Terraform Registry - Verified Modules"
     4  sidebar_current: "docs-registry-verified"
     5  description: |-
     6    Verified modules are reviewed by HashiCorp and actively maintained by contributors to stay up-to-date and compatible with both Terraform and their respective providers.
     7  ---
     8  
     9  # Verified Modules
    10  
    11  Verified modules are reviewed by HashiCorp and actively maintained by
    12  contributors to stay up-to-date and compatible with both Terraform and
    13  their respective providers.
    14  
    15  The blue verification badge appears next to modules that are verified.
    16  
    17  ![Verified module listing](/assets/images/docs/registry-verified.png)
    18  
    19  If a module is verified, it is promised to be actively maintained and of
    20  high quality. It isn't indicative of flexibility or feature support; very
    21  simple modules can be verified just because they're great examples of modules.
    22  Likewise, an unverified module could be extremely high quality and actively
    23  maintained. An unverified module shouldn't be assumed to be poor quality, it
    24  only means it hasn't been created by a HashiCorp partner.
    25  
    26  Module verification is currently a manual process restricted to a small group
    27  of trusted HashiCorp partners. In the coming months, we'll be expanding
    28  verification to enable the broader community to verify their modules.
    29  
    30  When [using registry modules](/docs/registry/modules/use.html), there is no
    31  difference between a verified and unverified module; they are used the same
    32  way.