Skip to content

Scarf tells you which companies download your package — LeadCognition tells you which developers are evaluating your tool, with contact info and AI outreach

Scarf Free (company-level only) Individual identity and outreach: not available
LeadCognition $99/mo Individual developer leads · email + LinkedIn · AI outreach

Scarf and LeadCognition are complementary tools that answer different questions. Scarf tells you which companies download your package. LeadCognition tells you which individual developer is evaluating your tool on GitHub, enriches them with verified contact data, and generates ready-to-send outreach.

No credit card required. No demo needed.

Scarf and LeadCognition are complementary tools that solve different but adjacent problems for DevTool companies. Many teams use both.

What Scarf does

Scarf’s Gateway tracks downloads of your npm, pip, Docker, or Helm package and maps them to companies. You see which organizations are actively downloading your library — useful for understanding adoption, prioritizing enterprise outreach, and detecting churn signals at the account level. The Apache Software Foundation, Linux Foundation, and CNCF have approved Scarf Gateway for OSS projects, which speaks to its approach to data collection.

Scarf AI (powered by Claude) adds AI-generated insights on top of usage analytics — still company-level, still analytics-focused.

What Scarf can’t do — and where LeadCognition fills the gap

Scarf resolves downloads to companies, not individuals. When Google downloads your npm package, Scarf tells you “Google.” It doesn’t tell you which engineer, what their GitHub profile is, what repos they’ve been active in, how to reach them, or what to say.

LeadCognition works at the individual developer level. When a developer stars your repo, forks a competing tool, opens an issue in your category, or makes a commit to an adjacent project — LeadCognition captures that signal, identifies the developer, enriches them with verified email and LinkedIn, and generates a personalized email grounded in what they actually did on GitHub.

The complementary stack

If you publish a package: use Scarf Gateway (free) for download analytics + company identification. Then use LeadCognition to find and contact the specific developers at those companies who are actively engaging with your GitHub repos. The signals are additive — package downloads tell you which companies, GitHub activity tells you which people.

LeadCognition vs Scarf — detailed comparison

Dimension LeadCognition Scarf
Entry price $99/mo (Starter) Free (Starter gateway)
Individual developer identity Yes — GitHub profile, name, email, LinkedIn No — company-level only
Contact enrichment Yes — verified email + LinkedIn per credit No — tells you companies, not people
AI outreach generation Ready-to-send email per lead No — analytics only
Package/download signals No — GitHub activity only Yes — npm, pip, Docker, Helm, custom SDKs
GitHub activity signals Primary focus — 10+ event types, continuous No — package downloads only
Foundation-approved / OSS-safe Operates on public GitHub API Yes — Apache, Linux Foundation, CNCF approved
Self-serve signup Yes — free tier, no card Yes — free gateway, no card
Outreach / sales workflow Built-in — signals → enrichment → AI outreach None — analytics platform only
Best for DevTool teams needing developer leads + outreach OSS maintainers tracking package adoption by company

All pricing published. No "Contact Sales."

Browse all leads free. Spend a credit to unlock verified email + LinkedIn for any lead.

Free
$0/mo
50 one-time trial credits
  • 2 sources · 1 discovery
  • LinkedIn + company reveals
  • 3-month signal backfill
Start Free
Starter
$99/mo
500 credits/month
  • 5 sources · 3 discoveries/month
  • Email + phone reveals, AI insights
  • 2 seats
Start Starter
Scale
$799/mo
8,000 credits/month
  • Everything in Business
  • 30 sources
  • Unlimited seats and discoveries
Start Scale

Frequently asked questions

What is Scarf and what does it do?

Scarf is an open source analytics platform that tracks package downloads across npm, pip, Docker Hub, Helm, and other package registries. It maps those downloads to companies using IP data — so OSS maintainers can see which companies are using their library. Scarf Gateway is free and has been approved by the Apache Software Foundation, Linux Foundation, and CNCF. Paid tiers add more monthly tracked companies, longer data retention, and additional seats.

How is LeadCognition different from Scarf?

Scarf and LeadCognition answer different questions. Scarf tells you 'Google downloaded your npm package 47 times this month.' LeadCognition tells you 'Sarah Chen at Google starred your repo on Tuesday, has 3 PRs in tools you compete with, and here's a personalized email to send her.' Scarf resolves downloads to companies. LeadCognition resolves GitHub activity to individual developers with contact info and outreach context.

Should I use Scarf or LeadCognition — or both?

Many DevTool teams use both because they're genuinely complementary. Scarf shows you which companies are downloading your package — good for understanding adoption at the company level. LeadCognition shows you which individual developers are engaging with your repo on GitHub — good for outreach and pipeline. If you publish an npm/pip/Docker package, Scarf Gateway is free and worth installing. If you want to turn GitHub engagement into leads and outreach, LeadCognition is purpose-built for that.

Does Scarf help with sales outreach?

No. Scarf is an analytics platform — it tells you about company-level usage patterns, not individual developers. There's no contact enrichment, no outreach generation, no lead scoring. If you want to act on the company signals Scarf surfaces (contact the right developer at that company, generate personalized outreach), you need a tool like LeadCognition.

Can LeadCognition detect package downloads like Scarf?

No. LeadCognition focuses on public GitHub activity — stars, forks, watches, PRs, issues, commits, releases, discussions. It does not track npm, pip, Docker, or Helm downloads. If your primary signal is package downloads rather than GitHub engagement, Scarf is the right tool for that signal. The two tools are additive.

See the developers already evaluating Scarf alternatives

Free tier, no credit card. 50 trial credits included.