What is Repo Intent Score? A 2026 Definition + Examples
Repo Intent Score — A Repo Intent Score is a numeric rating that measures how strongly the community around a single GitHub repository is currently evaluating a technology for real use. Where a Developer Signal Score ranks people, Repo Intent Score ranks repositories — it aggregates pull requests, issues, forks, and commits from every unique contributor over a recent window, weights them by event type and recency, and normalizes to a 0–100 scale. A high Repo Intent Score indicates a repo currently attracting hands-on evaluation, not just passive stargazers. Sales and investor teams use it to spot repositories trending into production usage before those trends are visible elsewhere.
Quick definition
- Numeric rating for a single GitHub repository based on aggregate evaluation activity
- Aggregates events from every unique contributor, not just the top few
- Weighted heavily toward pull requests, issues, and commits — not stars alone
- Applies recency decay across a 30-day window
- Normalized to 0–100 against a live distribution of comparable repos
- Useful for spotting technologies moving into production before market coverage
- Investors use it as an early indicator for infrastructure adoption
- Sales teams use it to prioritize accounts whose engineers are actively evaluating
How repo intent score works
The score begins with a count of GitHub events against the repository — pull requests merged or opened, issues filed, forks created, commits pushed to forks, and stars awarded. Passive signals like stars alone are downweighted heavily; active contribution carries most of the weight.
A recency decay is applied so events from the last 7 days dominate the score. A 60-day-old fork contributes almost nothing relative to a PR filed this week. This ensures the score tracks current momentum rather than cumulative historical popularity.
The number of unique contributors is a multiplier. A repo with 50 PRs from 5 people scores lower than a repo with 50 PRs from 40 people. Breadth of hands-on engagement is a stronger signal of real adoption than depth from a small core team.
Finally, the raw weighted sum is normalized against a live distribution of repos in the same technology category. A score of 85 means the repository is in the top 15% of activity in its category for the last 30 days, not a fixed event threshold.
Examples
Example 1 — Infrastructure trend spotting. A platform engineering team tracking competitor tools watches a new observability library climb from Repo Intent Score 30 to 78 over three weeks. The spike precedes mainstream coverage by roughly 45 days, giving the team a lead time to evaluate before the category shifts.
Example 2 — Account prioritization. An SDR team scores 400 repos in the data infrastructure category. The top 20 by Repo Intent Score surface which open-source projects their target accounts are contributing to — enabling far more specific outreach than a generic firmographic list.
Example 3 — Open-source funding. A VC evaluating dev-tool investments uses Repo Intent Score trajectory as one of five primary inputs for pipeline screening. Repos growing from 40 to 75 in 60 days enter the evaluation pipeline automatically.
Related concepts
Related glossary entries
Further reading
- GitHub stars to pipeline — the conversion math
- Stars vs. PRs vs. commits
- What is GitHub signal intelligence
Related tools
FAQ
What repositories can you score?
Any public GitHub repository can receive a Repo Intent Score — your own, competitor repos, or any open-source project. LeadCognition scans 30 days of GitHub Archive data for the repository and normalizes against peers in the same category.
How is Repo Intent Score different from GitHub stars?
Stars are a passive popularity signal that rarely correlates with production adoption. Repo Intent Score weights hands-on activity — pull requests, issues, and commits — far higher than stars. A repo with many stars but few PRs scores low; a repo with consistent PRs from distinct contributors scores high regardless of star count.
Why does breadth of contributors matter?
Activity from a small core team reflects the team itself, not external evaluation. A repo with PRs from 40 distinct companies signals broad hands-on adoption — a much stronger indicator of production use than concentrated activity from 5 maintainers.
Can Repo Intent Score predict category trends?
Yes — retrospective analysis shows coordinated score growth across a category typically precedes mainstream coverage by 30–60 days. It is one of the earliest quantitative indicators that a technology is moving into real use.
See also
Browse the full LeadCognition glossary or visit the 36-answer FAQ for site-wide coverage. If you are specifically evaluating tools, start with the free tools or the sales-tool comparisons.