SIGNAL SPEC: DEV-VELOCITY-V2.4 • FORENSIC CODE TELEMETRY

Developer velocity becomes a verifiable venture signal.

Twitter followers can be bought. Git commits can't. CodeQuity parses commit cadence, author diversity, PR review depth, and bot commit filters to isolate real builders from vanity hype.

Indexed Repos
4,200+
Protocols Tracked
Sybil Filter Precision
98.4%
Bot Churn Stripped
Refresh Frequency
< 4 hrs
Automated Git Sync
Alpha Lead Time
6–9 Mo
Precedes TGE Hype
Live Repository Signal Stream

Execution Telemetry: 365 Days of Code

Inspect commit cadence, contributor wave dynamics, and code delivery. Toggle between the playable arcade shooter and the 3D isometric skyline.

Signal Density
4.8x
Rolling 30D Velocity
Repo Events
2,789
Verified Commits & PRs
Contributor Diversity
14 Devs
0.82 Gini (Low Bus Factor)
Sybil Filter
Clean
0% Automated Bot Loops
LessMore
Game Mode
codequitycontributed2,789this year onGitHub
Source: GitHub REST/GraphQL API & On-Chain Contract Verify BridgeSample Dataset: 365 Days Rolling Velocity
Live Repository Scanner

Audit Any GitHub Repository

Type any open-source protocol repository to inspect its CodeQuity Traction Score, commit frequency, contributor breadth, and engineering velocity.

Composite Traction Engine v2.0

Analyze Any Web3 Startup

Input a GitHub URL to instantly generate a VC-grade traction score. We analyze developer velocity, community signals, and technical execution.

5-Pillar Model Deep Analytics VC Defensible
Scoring Dimensions

The 4 Forensic Code Diligence Pillars

How CodeQuity separates real technical momentum from cosmetic commit farming.

TEMPORAL MOMENTUM35% of Score

1. Rolling Commit Cadence

Sustained weekly delivery over 6 to 12 months rather than erratic bursts staged right before investor fundraising decks.

Positive Signal:Multi-author weekly commits, regular semantic version tagging, continuous branch activity.
Forensic Red Flag:Erratic bursts with 90+ days of inactivity; commits that surge only 7 days before round announcements.
DECENTRALIZATION30% of Score

2. Contributor Breadth & Bus Factor

Measures key-person risk. If 98% of code is written by a single anonymous engineer, protocol longevity is extremely fragile.

Positive Signal:Minimum 4+ core contributors reviewing each other's code; external community pull requests merged.
Forensic Red Flag:Single-author repository where solo founder force-pushes directly to main branch with zero reviews.
CODE DISCIPLINE20% of Score

3. PR Review Rigor & Merge Depth

Evaluates whether pull requests include meaningful discussion, architecture reviews, and automated CI test passes.

Positive Signal:Mandatory multi-peer approval checks, comprehensive unit/integration test suites, detailed PR descriptions.
Forensic Red Flag:Direct commits to main without PRs; zero testing framework; unreviewed contract deployments.
FORENSIC INTEGRITY15% of Score

4. Anti-Sybil & Bot Commit Filter

Isolates real smart contract logic and backend engineering from artificial whitespace, formatting, or README forks.

Positive Signal:Substantive diffs in smart contracts, zero-knowledge circuits, SDKs, and state-machine transitions.
Forensic Red Flag:Farmed commits that only edit markdown docs, bump version strings repeatedly, or auto-run GitHub action scripts.
Forensic Comparison Matrix

Real Builder vs. Vanity Token Project

How institutional crypto VCs detect the difference between sustainable protocols and synthetic marketing shells before capital commitment.

Evaluation MetricGenuine Builder ProtocolVanity Hype ProjectDiligence Impact
Commit DistributionSteady 365-day delivery wave across multiple branchesSudden 14-day spike right before fundraising announcementHigh risk of abandonment post-funding
Author Gini Coeff (Bus Factor)0.80–0.85 (12+ active engineers reviewing PRs)0.99 (Single developer writes 97% of code)Extreme key-person dependency
PR Review & Test Coverage> 80% test passes, 3+ review comments per PRDirect commits to main branch, 0 tests foundMassive smart contract exploit probability
Bot / Diff Quality FilterSolidity/Rust state transition & protocol logic80%+ diffs are README formatting or automated bot syncsArtificial metric pumping
24-Month Protocol Survival91% Survival & TVL Growth14% (86% abandoned post-TGE)Core leading indicator of fund return
Quantitative Weighting Algorithm

The Developer Velocity Scoring Formula

Normalized on a 0–100 scale using continuous mathematical decay models and commit diff AST analysis.

Dev_Velocity = (0.35 × Cadence) + (0.30 × Diversity) + (0.20 × PR_Rigor) + (0.15 × Releases)
Code Diligence Q&A

Frequently Asked Questions

Cosmetic gaming (e.g. repeated whitespace edits, automated bot commits, and script-run README forks) is stripped by CodeQuity's AST and Diff Forensics engine. We analyze AST node additions, cyclomatic complexity changes, author Gini coefficients, and PR review comments rather than raw commit counts.

Request access to score protocols with AI

Unlock investor memos, AI scoring, saved portfolios, and founder pipeline tools.

Request access