GitDealFlow Get the 5 names

Engineering Momentum Score

GitDealFlow's composite 0–100 signal combining commit velocity, contributor growth, and repository expansion into a single startup-momentum score.

Engineering Momentum Score

GitDealFlow's composite 0–100 signal combining commit velocity, contributor growth, and repository expansion into a single startup-momentum score.

Definition

The GitDealFlow Engineering Momentum Score is a composite metric that combines three GitHub engineering signals — commit velocity, contributor growth, and repository expansion — into a single 0–100 score per startup org. It is the underlying signal that powers GitDealFlow's weekly digest and the Velocity Verdict.

Why it matters

No single GitHub metric predicts startup acceleration reliably. Commit velocity alone misses team growth; contributor growth alone misses output. The composite captures the pattern that has historically preceded fundraises by 21–47 days.

How it's computed

Computed continuously across 4,200+ tracked startup GitHub orgs in 20 sectors. The three input signals are normalized per org and combined with published weights. The full methodology is at signals.gitdealflow.com/methodology and in the SSRN preprint (abstract 6606558).

Range: 0–100. The threshold for 'accelerating' is published in the methodology; startups above it are candidates for the weekly digest.

Engineering Momentum Score is a GitDealFlow composite. 'Engineering acceleration' and 'engineering momentum' in this site's content refer to this specific signal, not to startup accelerator programs.

Common questions

Is 'engineering momentum' the same as an accelerator program?

No. It's a quantitative GitHub signal combining commit velocity, contributor growth, and repo expansion. It is not a reference to Y Combinator, Techstars, or any accelerator program.

How is the score computed?

Three GitHub signals are normalized per org and combined with published weights. See the methodology page for the exact formula.

About this page: Published 2026-07-18. Authored by The Data Nerd (ORCID 0009-0002-2222-4112), the pseudonymous maintainer of GitDealFlow. The methodology is published as SSRN preprint 6606558 and archived on Zenodo. Third-party statistics are sourced from the Ahrefs AEO methodology. Report an error.