2017-08-15 22:36:32 +02:00
---
layout: "registry"
page_title: "Terraform Registry - Verified Modules"
sidebar_current: "docs-registry-verified"
description: |-
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.
---
# Verified Modules
2020-08-06 19:29:26 +02:00
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.
2017-08-15 22:36:32 +02:00
2020-08-06 19:29:26 +02:00
The verified badge appears next to modules that are published by a verified source.
2017-08-15 22:36:32 +02:00
2020-08-06 19:29:26 +02:00
![Verified module listing ](./images/registry-verified.png )
2017-08-15 22:36:32 +02:00
2020-08-06 19:29:26 +02:00
Verified modules are expected to be actively maintained by HashiCorp partners.
2020-01-28 19:51:40 +01:00
The verified badge isn’ t indicative of flexibility or feature support; very
2017-08-15 22:36:32 +02:00
simple modules can be verified just because they're great examples of modules.
Likewise, an unverified module could be extremely high quality and actively
maintained. An unverified module shouldn't be assumed to be poor quality, it
only means it hasn't been created by a HashiCorp partner.
When [using registry modules ](/docs/registry/modules/use.html ), there is no
difference between a verified and unverified module; they are used the same
way.