Contributor OSINT depth score
A dev identity & insider risk factor in the v1.7.0 rubric. Measured per protocol on a s cadence.
Methodology how we score #
**What this measures** This factor produces a curator-scored 1–5 depth score for each core contributor, based on the richness and independent corroborability of their online presence: LinkedIn profile depth (employment history, connections, endorsements), GitHub history (account age, contribution volume, fork and star patterns), conference or media presence, and any independent third-party references. The per-contributor scores are averaged to produce a team-level OSINT depth metric. Category 7 context: OSINT depth is a consolidated signal that partially overlaps with RD-F-112 (accountability surface count) but emphasizes depth and independence of evidence rather than breadth.
**Why it matters** A team member with a high-follower Twitter account and a LinkedIn profile created in the past six months with generic employment entries represents a different risk than one with a ten-year GitHub history, endorsed LinkedIn connections from verifiable prior colleagues, and three conference talk recordings. The distinction matters for assessing whether identity signals are genuine or fabricated. DPRK IT worker profiles consistently score low on OSINT depth — LinkedIn profiles are typically sparse, GitHub accounts are new, and conference references are absent. Legitimate senior DeFi contributors typically score 4–5 across all three evidence dimensions.
**Green / Yellow / Red** Green is scored when the team average OSINT depth score is 4 or above — multiple contributors with rich, independently corroborated online histories. Yellow applies when the average falls in the 2–3 range — some verifiable history exists but it is limited in depth or relies on easily-fabricated platforms. Red is scored when the team average falls below 2 — most or all contributors have shallow or unverifiable online presences inconsistent with the experience level claimed.
**Common gray cases** Gray is assigned when the curator cannot complete the OSINT assessment within the evidence budget because the team has not disclosed sufficient identity information to begin the scoring process.
**Notable historical examples** No cross-hacked incidents currently linked in database for this factor.
Measurement what to look for #
Curator-scored 1–5 based on LinkedIn depth, GitHub history, conference presence per contributor.