The Problem Businesses that need large‑scale Google Maps lead lists must either pay for SaaS services or write their own scrapers, both of which involve handling pagination, rate limits, and data enrichment. The repository promises a ready‑made tool that extracts 50+ fields (emails, phones, social profiles, reviews) and offers an API, aiming to reduce the engineering effort required for lead generation.

What This Does The project is positioned as a full‑stack scraper with enrichment and API access. The public artefacts – README.md, advanced.md, fields.md, server-deployment.md and the extensive screenshots/ collection – describe UI screens, pricing, and feature lists, but the source code that drives the scraper is not present in the checkout. Consequently, there is no visible implementation of crawling, parsing, or API routing.

How It Is Wired The repository does not expose an entry‑point script (e.g., main.py, index.js) or any language‑specific modules. The only executable‑related file is a single test file (name not listed), which cannot be linked to functional code. Because the call graph cannot be constructed from the current file set, the wiring is effectively undocumented. The documentation suggests the following logical flow, inferred from the UI‑focused assets:

  1. User interface – implied by screenshots such as screenshots/homepage.png and screenshots/run.png.
  2. Backend processing – referenced in server-deployment.md, which outlines a deployment model but provides no code (no Dockerfile, no server scripts).
  3. Enrichment – mentioned in advanced.md and shown in screenshots/enrichment-results.png, yet no enrichment modules are present.

Without concrete source files, the repository cannot be traced from “run” command to network calls or file writes. The wiring therefore remains unmapped.

How To Use It The documentation lists usage steps, but the repository lacks the scripts those steps would invoke.

Setup – No package.json, requirements.txt, pyproject.toml, or Makefile exists, so an install command cannot be derived.

Configuration – No .env.example, config.yaml, or similar file is present; the README mentions API keys (e.g., “api‑key‑omkar.png”) but does not provide a location for storing them.

Running – No CLI entry point (cli.py, run.sh, etc.) can be identified. The only actionable file is the test suite; however, without the underlying implementation the test cannot be executed meaningfully.

If the missing code were added, a typical workflow would be:

# hypothetical install (requires a package manager)
npm install   # or pip install -r requirements.txt
# set required env vars (e.g., GOOGLE_MAPS_API_KEY)
export GOOGLE_MAPS_API_KEY=your_key
# launch the scraper
python -m googlemaps_scraper  # or node src/index.js

Real‑World Use A company could embed the scraper behind a microservice that receives a JSON payload { "query": "restaurants in NYC", "radius": 5000 }, calls the internal crawling routine, enriches results via third‑party email finders, and returns a CSV. The current repo does not provide the microservice code, so the integration would need to be built from scratch.

Code Health & Issues

  • Med – No CI/CD pipeline – No .github/ workflows, no Jenkinsfile, and no automated test gate.
  • Med – Missing build artefacts – No Dockerfile, Makefile, or language‑specific lockfile; reproducible builds are not defined.
  • Low – License present – LICENSE file exists, fulfilling open‑source licensing.
  • Low – Tests present but orphaned – One test file exists, but without accompanying source code it cannot be executed.
  • Low – No committed secrets – Static scan found no secret values in the repo.

The Bottom Line The repository supplies extensive marketing and UI documentation but does not include the scraper’s executable code, configuration files, or build instructions. Engineers interested in the described functionality will need to locate the missing source (likely in the upstream omkarcloud/google-maps-scraper project) or implement their own scraping pipeline. The project is suitable as a reference for UI/feature design, not as a drop‑in codebase.