Every design system has a gap between what it offers and what gets written. You can argue about that gap in the abstract for a long time. I wanted to look at it in real code, change by change, so I took a popular open-source document-sharing product and replayed its last hundred merged changes against the components and tokens it has today.
This is what I found, how I checked it, and why the product stays anonymous.
The method
The idea is simple. Take a repository's recent history and, for each merged change, ask one question: did this change add something the codebase already had?
For each change, the check looks only at the lines that change added, not the whole file it touched. It compares them with the components and design tokens the repository declares.…