What is Signal Strength Score? A 2026 Definition + Examples
Signal Strength Score — A Signal Strength Score rates the quality of a single GitHub event or event cluster on a four-part rubric: volume, recency, event-type quality, and topical diversity. Where a Developer Signal Score rolls up an engineer's full activity and a Repo Intent Score rolls up a repository's, a Signal Strength Score zooms in on individual events — the issue one developer filed this morning, the PR another merged last night. It answers the question, "how strong is this specific signal, right now?" and sorts an inbound event feed so sales teams act on the strongest evidence first.
Quick definition
- Rates a single GitHub event or cluster, not a developer or a repo
- Four factors — volume (30%), recency (30%), quality (25%), diversity (15%)
- Quality means event type: PR and issue outweigh fork, which outweighs star
- Diversity rewards engagement across multiple related repos
- Output: Weak, Moderate, Strong, or numeric 0–100
- Used to sort real-time event feeds and trigger alerts
- A single PR on a hot repo can outrank hundreds of stars
- Recency decay weights today's events roughly 2x events from last week
How signal strength score works
Volume counts how many events the developer generated in the current window. One issue is weaker than three issues. But volume is capped — fifty stars does not beat one PR, because the quality component dominates.
Recency applies a time decay curve. Events in the last 24 hours get a ~2x multiplier, events in days 1–7 count at 1x, and events older than 30 days contribute almost nothing. Hot events dominate the feed, which is the point of a real-time signal.
Quality ranks event types on a fixed rubric: pull request merged (10), issue opened with enterprise keywords (9), issue opened (8), fork (5), commit to fork (4), star (1). A star from an engineer at a Series A company rates a 1; a PR opened by the same engineer rates a 10.
Diversity rewards breadth. A developer who engages on three related repos in your category scores higher than one who engages with three events on the same repo. The idea is that breadth signals category-level evaluation, not one-off interaction.
Examples
Example 1 — Inbound feed sort. LeadCognition streams 40,000 events per day against monitored repos. Signal Strength Score sorts the feed top-down, pushing the 50 strongest signals to the front so an SDR opens each morning to the highest-intent activity, not a chronological firehose.
Example 2 — Alert threshold. A revenue operations team sets a threshold of Strong (≥75) for automated Slack alerts to the AE owning the account. Below 75, the event goes into a daily digest. This keeps alerts rare enough that the AE pays attention when they fire.
Example 3 — Decay validation. Retrospective analysis at one DevTool company showed that outreach within 48 hours of a Strong signal converted at 4.1x the rate of outreach 7–14 days later — direct evidence that recency decay in the scoring model is justified.
Related concepts
Related glossary entries
Further reading
- Why GitHub activity is the strongest buying signal
- Signal-based selling playbook
- Identifying high-intent developers on GitHub
Related tools
FAQ
Is Signal Strength Score the same as Developer Signal Score?
No. Signal Strength Score rates a single event or cluster. Developer Signal Score rolls up a developer's full activity into a per-person rating. The two compose — a developer with many Strong events has a high Developer Signal Score.
What is the Strong threshold?
In LeadCognition's default model, any event scoring ≥75 on the 0–100 scale is tagged Strong. 50–74 is Moderate, below 50 is Weak. The thresholds are tunable per workspace.
Can a star ever score Strong?
Rarely. A star from an engineer at a known enterprise target company, on a repo that the company has not engaged with before, can cross into Moderate with the diversity multiplier — but it takes unusual conditions. PRs and issues are the native Strong-scoring event types.
Does Signal Strength decay over time?
Yes. The recency factor drops a Strong signal toward Moderate within 7 days and toward Weak by day 30. This is intentional — buying intent fades as the developer's attention moves on.
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.