Terraform Registry Scraper

Export structured public Terraform Registry infrastructure modules for discovery, comparison, monitoring, and governance.

What you get

Search the public Terraform Registry catalog and save one deduplicated row per infrastructure module. Results include module address, version, provider, description, download count, verification, publication time, source identity, and bounded input, output, resource, and submodule counts. Use discovery inputs for market maps and exact-name inputs, when available, for stable monitoring cohorts.

Output fields

Field group	Description
Identity	Canonical address, display name, and source URL.
Release evidence	Current version or tag data and source timestamps when published.
Adoption signals	Public download, install, pull, star, or rating metrics available from the source.
Ownership and links	Public author, owner, project, repository, documentation, or homepage references.
Classification	Public tags, categories, keywords, packaging, or status values.
Provenance	Search query and named upstream source for traceable analysis.

Example output

{"address":"terraform-aws-modules/vpc/aws","version":"6.0.1","provider":"aws","downloads":100000000,"verified":true,"publishedAt":"2026-07-01T00:00:00Z","inputCount":100,"url":"https://registry.terraform.io/modules/terraform-aws-modules/vpc/aws/latest"}

Input parameters

Parameter	Required	Description
queries	No	Up to five module search phrases.
moduleAddresses	No	Up to 25 namespace/name/provider addresses or URLs.
provider	No	Optional provider filter.
verifiedOnly	No	Restrict discovery to verified modules.
maxResultsPerQuery	Yes	Maximum modules per query; defaults to 25.
maxResults	Yes	Maximum unique modules across all modes; defaults to 100.

At least one discovery or exact-name input is required. Result limits apply after cross-input deduplication, and only saved unique rows are charged.

Use cases

• Developers: discover alternatives and compare public release evidence.
• Platform teams: monitor versions, tags, compatibility, and activity for a fixed portfolio.
• Security teams: build an evidence inventory before joining vulnerability and deployment data.
• Product researchers: map a developer ecosystem with repeatable queries and dated snapshots.

Limitations

Only public registry modules are covered. The Actor deliberately excludes large README bodies and does not interpret module quality, security, or cloud cost from popularity and interface counts.

Compared to alternatives

Current Apify Store alternatives include crawlerbros/terraform-registry-scraper and parseforge/terraform-registry-modules-scraper. Thirdwatch combines discovery and bounded monitoring inputs where the source permits them, saves canonical evidence URLs, deduplicates before charging, provides exactly four PPE tiers, and ships ten ready-to-save Task recipes plus a five-article workflow library. Compare current Store listings directly because competitor features and pricing can change.

FAQ

Does this Actor access private packages or accounts?

No. It collects only metadata available from the public source and does not sign in, bypass access controls, or request private registry credentials.

How should I monitor a fixed portfolio?

Use exact names where supported, keep result limits explicit, save the input as an Apify Task, and retain dated datasets. Do not let an empty or failed run overwrite the previous successful snapshot.

Are popularity metrics quality or security scores?

No. Downloads, installs, pulls, stars, and ratings help prioritize review, but they do not replace vulnerability, provenance, license, maintainership, or internal deployment evidence.

Where can I find more workflows?

Visit Thirdwatch developer-data scrapers and the related GitHub, npm, and OSV Actors.

Last verified: 2026-07