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.
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.
Audit Any GitHub Repository
Type any open-source protocol repository to inspect its CodeQuity Traction Score, commit frequency, contributor breadth, and engineering velocity.
The 4 Forensic Code Diligence Pillars
How CodeQuity separates real technical momentum from cosmetic commit farming.
1. Rolling Commit Cadence
Sustained weekly delivery over 6 to 12 months rather than erratic bursts staged right before investor fundraising decks.
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.
3. PR Review Rigor & Merge Depth
Evaluates whether pull requests include meaningful discussion, architecture reviews, and automated CI test passes.
4. Anti-Sybil & Bot Commit Filter
Isolates real smart contract logic and backend engineering from artificial whitespace, formatting, or README forks.
Real Builder vs. Vanity Token Project
How institutional crypto VCs detect the difference between sustainable protocols and synthetic marketing shells before capital commitment.
| Evaluation Metric | Genuine Builder Protocol | Vanity Hype Project | Diligence Impact |
|---|---|---|---|
| Commit Distribution | Steady 365-day delivery wave across multiple branches | Sudden 14-day spike right before fundraising announcement | High 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 PR | Direct commits to main branch, 0 tests found | Massive smart contract exploit probability |
| Bot / Diff Quality Filter | Solidity/Rust state transition & protocol logic | 80%+ diffs are README formatting or automated bot syncs | Artificial metric pumping |
| 24-Month Protocol Survival | 91% Survival & TVL Growth | 14% (86% abandoned post-TGE) | Core leading indicator of fund return |
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)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.