Homebrew Formula Scraper — Dev-Tool Vendor Leads
Pricing
from $6.00 / 1,000 leads
Homebrew Formula Scraper — Dev-Tool Vendor Leads
Scrape the Homebrew registry for software companies and developer-tool vendors behind macOS formulas and casks. Returns vendor homepage, license, version, and dependencies. Filter by keyword and company URLs only. B2B leads for the devtools market. CSV/JSON/Excel export.
Pricing
from $6.00 / 1,000 leads
Rating
0.0
(0)
Developer
GoCreative AI
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
📊 Example output (real run)

A real record from a live run — clean structured data, exported as CSV / JSON / Excel or via API.
Find the software companies and developer-tool vendors behind Homebrew packages. Every CLI tool, database, infra utility, and Mac app distributed through Homebrew points back to a vendor homepage — this actor turns that into a clean B2B lead list for the developer-tools market.
Ideal for anyone selling to (or hiring from) devtool, DevOps, infrastructure, and open-source software companies.
What you get
| Field | Description |
|---|---|
name | Formula or cask name |
type | formula (CLI) or cask (GUI app) |
description | Package description |
homepage_url | Vendor homepage — the outreach target |
license | Software license (OSS vs commercial signal) |
version | Current version |
runtime_dependencies | Up to 10 runtime deps (tech-stack signal) |
build_dependencies | Up to 5 build deps |
homebrew_listing_url | Direct link to the Homebrew listing |
Inputs
| Input | Type | Default | Notes |
|---|---|---|---|
keywords | array | [] | Only keep packages whose name/description matches these keywords |
includeCasks | boolean | true | Include GUI apps (casks), not just CLI formulas |
companyUrlsOnly | boolean | true | Drop generic/personal pages — keep real company homepages |
maxResults | integer | 500 | Cap on rows returned |
Example use cases
- Sell developer & DevOps tooling — CI/CD, observability, security, and cloud vendors targeting toolmakers.
- Ecosystem / partnership outreach — reach the maintainers behind widely-installed formulas.
- Competitive research — map an entire category (e.g.
database,kubernetes,terraform) by license and dependencies. - Tech-stack enrichment — use
runtime_dependenciesto infer what a vendor's product is built on.
Why this beats a raw package dump
companyUrlsOnly filters out personal GitHub pages and generic hosts so you keep real company homepages you can actually sell to. license separates open-source projects from commercial vendors, and dependency lists give you a free tech-stack signal for personalization.
Output formats
Export to CSV, JSON, or Excel, or pull results via the Apify API into your CRM, Clay table, or outreach sequence.
Tips
- Pass targeted
keywords(e.g.["kubernetes","docker","terraform"]) to build a category-specific vendor list. - Keep
companyUrlsOnly=truefor outreach lists; set itfalseonly when you want the full ecosystem including individual maintainers.