Engineering acceleration
A signal type indicating general engineering acceleration that does not fit the hiring burst, infrastructure buildout, or deploy spike categories. Framework migrations often indicate a technology stack transition — moving from a prototype stack to a production stack, or adopting new infrastructure. This is the subtlest signal type but can indicate the shift from exploration to exploitation, a key milestone in startup development.
Formal signal definition
Framework Migration is also a formal signal primitive in the VC Deal Flow Signal methodology, with a published formula, decision rule, and pitfall analysis.
Read the signal definition →Metrics, signal types, and decision rules from the methodology.
The named mechanism behind VC Deal Flow Signal.
The total number of commits to a startup's most active public GitHub repository over a rolling 14-day window.
The percentage change in commit velocity compared to the preceding 14-day window.
A sustained increase in a startup's engineering output relative to its own historical baseline.
Any data-driven indicator that helps an investor identify a promising startup before traditional deal sourcing channels surface it.
The change in the number of unique contributors to a startup's GitHub repository over time.
A signal type indicating that a startup's contributor growth rate exceeds 50% in a short window.
A signal type indicating that a startup has created three or more new public repositories in 30 days.
This definition is published under CC BY 4.0. Cite as:
The Data Nerd. "Framework Migration." VC Deal Flow Signal Glossary, https://signals.gitdealflow.com/define/framework-migration.
The free Acceleration Watch turns terms like Framework Migration into five named, accelerating startups every Sunday — translated into plain English, 21 to 47 days before the deck circulates. No code-reading, no card.