Scan recent activity
Paste a public repo. The tool checks public GitHub signals that show whether developers are actively evaluating it.
Free Developer Tool
GitHub Developer Dossier
Enter any GitHub username — get influence tier, activity cadence, tech stack, recent stars, and social graph in one view.
How it works
Weight intent signals
Forks, issues, freshness, and repo momentum matter more than passive awareness. Stars are useful, but they are not the whole story.
Read the score
Use the 0-100 score as a first-pass signal. High scores mean the repo deserves closer monitoring and contact discovery.
What the score means
High intent
Strong public activity. This is a good candidate for deeper account research and developer contact discovery.
Moderate intent
There is visible activity, but it needs context from company fit, category overlap, and recent events.
Low signal
Mostly passive or stale public signal. Track it if the repo is strategic, but avoid over-prioritizing it.
Frequently asked questions
What data powers the score?
The Astro tool currently uses public GitHub API data as a lightweight landing-page proxy. LeadCognition’s product scoring goes deeper with monitored repo activity and enriched lead context.
Why does the free tool not show every evaluator?
The free tool shows whether the repo has visible signal. LeadCognition is where you unlock names, companies, verified contact paths, and outreach context.
A GitHub developer dossier is a single view of what a username actually tells you about the human behind it: how much reach they have, whether they are still active, what they build with, what they are evaluating right now, and where else they exist online.
The profile page won’t give you that. It gives you a follower count and a wall of repositories, and leaves the judgement to you. This tool does the judgement — reading the public GitHub API and computing the same signals the paid dossier endpoint returns, using the same thresholds.
Free, no signup, and it runs entirely in your browser against GitHub’s public API.
What the dossier computes
Influence tier
Follower count bucketed three ways, because a number nobody has calibrated is not a decision input.
- Major — 10,000+ followers. Ecosystem-level reach. When this person stars something, other people notice.
- Notable — 1,000–9,999 followers. Recognised inside their niche.
- Contributor — under 1,000. Building rather than broadcasting, which is most working engineers and most of your actual buyers.
Deliberately coarse. A three-way split you can route on beats a decimal score nobody trusts.
Activity cadence
Derived from the most recent public event, falling back to the most recent push.
- Daily — active in the last 7 days
- Weekly — last 30 days
- Monthly — last 90 days
- Dormant — nothing public in over 90 days
This is the single cheapest disqualifier in developer outbound. An account that last pushed eighteen months ago isn’t evaluating your product, and no amount of personalization changes that.
Tech stack
The primary languages across their non-forked public repositories, ranked by repository count. Forks are excluded on purpose — forking a Rust project says nothing about whether someone writes Rust.
Recently starred repos
Up to ten of the most recently starred repositories, newest first — not the most-starred ones.
This is the most honest intent signal on a GitHub profile. A star from last week says what someone is evaluating now. A star from 2019 says what they were evaluating in 2019. Sorting by stars-received would surface the second and bury the first.
Company, location, role signal
The employer and location fields where the developer filled them in, plus a role inferred from bio text — Founder, DevRel, Data, Designer, or nothing.
Nothing is a real answer here. When the bio doesn’t support a category the tool says so instead of guessing — the same reason de-anonymization returns nothing rather than a maybe.
Followers, repos and social graph
Follower, following and public-repo counts, account age, open-to-work flag, and any social accounts the developer has linked from their profile.
Self-linked accounts matter more than they look: they are the highest-trust identity signal on a GitHub profile, because the developer put them there deliberately. They are often the shortest path from a handle to a real name.
What this tool cannot do
It reads public GitHub data only, so:
- It won’t find an email. Only about 15% of GitHub users expose one, and this tool doesn’t read commit metadata. Use the GitHub Email Finder for that.
- It won’t find a LinkedIn profile. That requires identity resolution against sources outside GitHub — see GitHub to LinkedIn.
- It’s rate-limited. GitHub’s unauthenticated API allows 60 requests per hour per IP, and a full dossier uses up to 5. Empty sections usually mean you hit that ceiling, not that the profile is bare. Wait an hour, or use the API with a key.
- It works on public accounts. There’s nothing to read on a private one.
From free lookup to a working pipeline
The free tool answers one handle at a time. The paid dossier is the same computation behind an API, plus the parts this page cannot do:
| This free tool | Dossier API | De-anonymization API | |
|---|---|---|---|
| Influence, cadence, stack, stars, socials | Yes | Yes | With the dossier toggle |
| Batch lookup | No | Yes | Up to 50 per request |
| Verified LinkedIn identity | No | No | Yes |
| Cost | Free | 1 credit | 2 credits, on match only |
Signup is 50 credits with no credit card, and API keys are available on the free tier — so 50 dossiers, or 25 identity resolves, cost nothing to evaluate.
Get an API key — free, no card See the dossier API →
Frequently Asked Questions
Is this really free?
Yes, and there’s no signup. It calls GitHub’s public API directly from your browser, so nothing you type reaches our servers. The limit is GitHub’s own: 60 unauthenticated requests per hour per IP.
Why is a section empty?
Almost always the rate limit. A full dossier makes up to five GitHub API calls, and the unauthenticated allowance is 60 per hour per IP. It degrades instead of failing: you get whatever it managed to fetch. Wait an hour, or use the API with a key.
Does the free tool match the paid dossier?
The influence, cadence and role thresholds are identical — the same numbers, kept in sync deliberately so the free tool and the API never disagree about the same developer. The API adds batch lookup, idempotent per-handle charging, and the option to attach a verified LinkedIn identity to the same call.
Can I look up several developers at once?
Not here — it’s one handle at a time. POST /api/v1/dossier handles them programmatically at 1 credit each, and POST /api/v1/deanon/batch takes up to 50 handles per request.
Is looking this up allowed?
Everything shown comes from GitHub’s public API — the same data any visitor sees on the profile page, just computed instead of listed. See the privacy policy for how LeadCognition handles data, including removal requests.
Ready when you are
Start with developers already showing intent.
Create a free workspace, browse public signal, and unlock contacts only when the account is worth pursuing.