LeadFlow
PassAudited by ClawScan on May 1, 2026.
Overview
LeadFlow is a coherent lead-generation CLI, but it uses third-party API keys, bulk scraping/enrichment, local lead storage, and optional webhook export, so users should install and run it deliberately.
Install only after verifying the npm package provenance. When using it, provide explicit scope, limits, and destinations; monitor API usage and costs; keep API keys private; and treat generated lead databases, exports, and webhook payloads as sensitive business data.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The tool can make many external requests and may consume API quota or create compliance/terms-of-service issues if used too broadly.
The implementation supports automated scraping requests with proxy use and user-agent rotation. This fits the lead-scraping purpose, but users should ensure they have permission and keep scraping scope limited.
Create an HTTP client for scraping (proxy + user agent rotation) ... useProxy: true, rotateUserAgent: true
Use explicit locations, trades, limits, and dry runs; confirm that your scraping and enrichment use complies with provider terms and applicable privacy rules.
Incorrectly scoped or exposed API keys could lead to unwanted usage, costs, or account abuse.
The skill expects provider API credentials for its stated functionality. The credentials are disclosed and purpose-aligned, but they authorize paid third-party services.
Required: `GOOGLE_PLACES_API_KEY` ... Optional enrichment/verification keys ... `HUNTER_API_KEY` ... `APOLLO_API_KEY` ... `TWILIO_AUTH_TOKEN`
Use least-privilege API keys where possible, monitor provider usage, and do not share exported logs or outputs that reveal credentials.
A packaging mismatch can make it harder to confirm exactly which package lineage and executable are being installed.
The lockfile identity differs from the skill/package name `leadflow` shown elsewhere, which is a package consistency and provenance note rather than direct evidence of malicious behavior.
"name": "leadscrape-pro" ... "bin": { "leadscrape": "dist/cli.js" }Before installing, verify the npm package name, version, repository, and published tarball contents match the LeadFlow project you intend to use.
Stored lead lists may include names, emails, phone numbers, and business details that should be handled as sensitive business data.
The tool persists lead data locally and writes exports, which is expected for a lead-list workflow but means contact data can remain on disk after use.
DATABASE_PATH: z.string().default('./data/leads.db') ... EXPORT_PATH: z.string().default('./data/exports')Store the database and exports in an appropriate location, restrict access, and delete old lead data when it is no longer needed.
If the wrong webhook URL is used, lead data could be sent to an unintended third party.
The webhook feature sends lead data to a user-supplied external URL. This is disclosed and purpose-aligned for automation, but it creates an outbound data-sharing path.
leadflow webhook -u "https://hooks.zapier.com/hooks/catch/..." --status verified --json ... POSTs leads as JSON to the URL
Only use webhook URLs you control or trust, confirm the destination before sending, and apply filters/limits to minimize shared data.