🧱 Terraform Registry Modules Scraper

🚀 Pull Terraform module metadata in seconds. Turn the public HashiCorp Terraform Registry into a clean feed of modules with version, owner, source repo, download counts, and verified status.

🕒 Last updated: 2026-06-05 · 📊 14 fields per record · Thousands of public modules · Every provider in the registry

Browse and collect module metadata straight from the official Terraform Registry public API. List the most recently published modules, search by keyword, or narrow by provider and namespace. Each module becomes one structured record you can drop into a spreadsheet, a database, or a dependency dashboard.

Coverage spans the whole public registry: AWS, Google Cloud, Azure, Kubernetes, Oracle, Docker, and any other provider that publishers ship modules for. Records include verified status so you can tell official partner modules apart from community ones.

🎯 Target Audience	💡 Primary Use Cases
Platform and DevOps engineers	Discover and compare infrastructure modules
Cloud architects	Track module versions and source repositories
Security and compliance teams	Audit module provenance and verified status
Data and research teams	Map the Terraform module ecosystem

📋 What the Terraform Registry Modules Scraper does

This Actor reads the HashiCorp Terraform Registry public API and returns one record per module. For every module it captures the identifier, namespace, name, provider, latest version, owner, description, source repository URL, version tag, publish date, download count, and verified flag. You can list the latest modules, run a keyword search, or filter by provider and namespace.

🎬 Full Demo (🚧 Coming soon)

⚙️ Input

All inputs are optional. With no input the Actor lists the most recently published modules in the registry.

Field	Type	Description
searchQuery	string	Keyword to search modules by, for example vpc or eks. Leave empty to list the latest modules.
provider	string	Provider to filter by, for example aws, google, azurerm.
namespace	string	Publisher namespace to filter the listing by, for example terraform-aws-modules. Ignored when a search query is set.
maxItems	integer	Cap on how many module records are produced. Free plan is limited to 10.

Example 1. List the latest modules.

{
    "maxItems": 25
}

Example 2. Search VPC modules on AWS.

{
    "searchQuery": "vpc",
    "provider": "aws",
    "maxItems": 50
}

⚠️ Good to Know: The Terraform Registry namespace filter applies only to the plain listing, not to keyword search. When you set a searchQuery, the namespace value is ignored and results come from the registry search ranking.

📊 Output

Each record describes one Terraform module.

Field	Description
🆔 id	Full module identifier (namespace/name/provider/version)
🏷 namespace	Publisher namespace
📦 name	Module name
☁️ provider	Target provider
🔖 version	Latest published version
👤 owner	Registry account that owns the module
📝 description	Module description
📂 sourceUrl	Source repository URL
🔖 tag	Git tag for the latest version
🕒 publishedAt	Publish timestamp of the latest version
⬇️ downloads	Total download count
✅ verified	Whether the module is verified by HashiCorp
🔗 url	Public registry page for the module
🕒 scrapedAt	When the record was collected

Sample records from a live run:

{
    "id": "GoogleCloudPlatform/lb-http/google/14.2.0",
    "namespace": "GoogleCloudPlatform",
    "name": "lb-http",
    "provider": "google",
    "version": "14.2.0",
    "owner": "danisla",
    "description": "Creates a global HTTP load balancer for Compute Engine by using forwarding rules",
    "sourceUrl": "https://github.com/terraform-google-modules/terraform-google-lb-http",
    "tag": "v14.2.0",
    "publishedAt": "2026-01-15T00:10:36.13339Z",
    "downloads": 10521796,
    "verified": true,
    "url": "https://registry.terraform.io/modules/GoogleCloudPlatform/lb-http/google",
    "scrapedAt": "2026-06-05T17:19:02.613Z",
    "error": null
}

{
    "id": "GoogleCloudPlatform/managed-instance-group/google/1.1.15",
    "namespace": "GoogleCloudPlatform",
    "name": "managed-instance-group",
    "provider": "google",
    "version": "1.1.15",
    "owner": "danisla",
    "description": "Modular Google Compute Engine managed instance group for Terraform.",
    "sourceUrl": "https://github.com/GoogleCloudPlatform/terraform-google-managed-instance-group",
    "tag": "1.1.15",
    "publishedAt": "2019-02-14T16:55:26.567562Z",
    "downloads": 175062,
    "verified": true,
    "url": "https://registry.terraform.io/modules/GoogleCloudPlatform/managed-instance-group/google",
    "scrapedAt": "2026-06-05T17:19:02.775Z",
    "error": null
}

{
    "id": "GoogleCloudPlatform/lb-internal/google/9.0.4",
    "namespace": "GoogleCloudPlatform",
    "name": "lb-internal",
    "provider": "google",
    "version": "9.0.4",
    "owner": "danisla",
    "description": "Creates an internal load balancer for Compute Engine by using forwarding rules",
    "sourceUrl": "https://github.com/terraform-google-modules/terraform-google-lb-internal",
    "tag": "v9.0.4",
    "publishedAt": "2026-06-05T06:17:56.286307Z",
    "downloads": 5349203,
    "verified": true,
    "url": "https://registry.terraform.io/modules/GoogleCloudPlatform/lb-internal/google",
    "scrapedAt": "2026-06-05T17:19:02.820Z",
    "error": null
}

✨ Why choose this Actor

• Reads the official public Terraform Registry API, so the data matches what you see on the registry website.
• One clean record per module with consistent fields, ready for analysis.
• Verified flag included, so you can separate HashiCorp partner modules from community ones.
• Flexible inputs: list the latest modules, search by keyword, or filter by provider and namespace.
• No API key or login required.

📈 How it compares to alternatives

Approach	Setup	Structured output	Verified flag	Maintenance
This Actor	None	Yes	Yes	Handled for you
Manual browsing of the registry	High	No	Manual	Ongoing
Writing your own API client	Medium	Build it yourself	Build it yourself	On you

🚀 How to use

1. Sign up for a free Apify account using this link.
2. Open the Terraform Registry Modules Scraper.
3. Leave the input empty for the latest modules, or add a search query, provider, or namespace.
4. Click Start and let the run finish.
5. Open the results and review or connect them to your tools.

💼 Business use cases

Platform engineering

Goal	How this helps
Build an internal module catalog	Pull modules by provider or namespace and keep a single list
Track upgrades	Compare versions and publish dates across runs

Security and compliance

Goal	How this helps
Audit provenance	Capture source repository URLs and owners for every module
Flag unverified modules	Filter records by the verified field

Vendor and ecosystem research

Goal	How this helps
Measure adoption	Use download counts as a popularity signal
Map publishers	Group modules by namespace and provider

Tooling and automation

Goal	How this helps
Feed dashboards	Push records into a database or BI tool
Trigger alerts	Watch for new versions of modules you depend on

🔌 Automating Terraform Registry Modules Scraper

Connect the output to the tools your team already uses:

• Make and Zapier for no-code workflows.
• Slack to post new or updated modules to a channel.
• Airbyte to sync records into a warehouse.
• GitHub to open issues when a tracked module ships a new version.
• Google Drive to archive snapshots of the catalog.

🌟 Beyond business use cases

• Research: study how the Terraform module ecosystem grows over time.
• Personal: keep a watchlist of modules you use in side projects.
• Non-profit: maintain a shared catalog of vetted infrastructure modules.
• Experimentation: prototype dependency graphs and popularity rankings.

🤖 Ask an AI assistant

Paste a few records into your favorite assistant and ask it to summarize, rank, or compare:

• ChatGPT
• Claude
• Perplexity
• Microsoft Copilot

❓ Frequently Asked Questions

Does this need a Terraform Registry API key? No. The registry public API is keyless.

How many modules can I collect? Free plan runs are limited to 10 records. Paid plans can collect far more, up to your configured cap.

Can I search by keyword? Yes. Set the search query field and the Actor uses the registry search endpoint.

Can I filter by provider? Yes. The provider filter applies to both listing and search.

Can I filter by namespace? Yes for plain listing. When a search query is set, the namespace value is ignored.

What does the verified flag mean? It indicates whether HashiCorp has verified the module as an official partner module.

Where does the owner value come from? The Actor enriches each module with the owner from the registry module detail endpoint.

Is the download count cumulative? Yes. It reflects total downloads reported by the registry.

Does it include the source repository? Yes, when the registry exposes a source URL for the module.

How fresh is the data? Each run reads live from the registry, so values match the registry at run time.

Can I run this on a schedule? Yes. Use the Apify scheduler to run it as often as you need.

🔌 Integrate with any app

Every run produces structured records you can pull through the Apify API or connect to Make, Zapier, and other platforms. Wire the output into spreadsheets, databases, dashboards, or messaging tools.

🔗 Recommended Actors

• deps.dev Package Insights Scraper
• Libraries.io Scraper
• crt.sh Certificate Transparency Scraper
• SEC XBRL Company Facts Scraper

💡 Pro Tip: browse the complete ParseForge collection.

🆘 Need Help? Open our contact form

⚠️ Disclaimer: independent tool, not affiliated with HashiCorp or Terraform. Only publicly available data collected.