What top GitHub profile READMEs actually contain

The finding

Most top accounts keep the profile README short, or skip it. Of the 44 most-followed accounts checked, 25 have none. Across all 30 READMEs found, the median is about 20 lines. Three embed a stats widget. None uses a typing-animation header.

Stats cards, a typing header and a wall of badges are not what these accounts do. Their audiences sit on repositories: the median most-starred repo among the 30 has 9,115 stars. The README is the least of it.

The data

Accounts checked: 62. That is the 44 most-followed on the top-300 list, plus the 9 most-followed of each of two peer sets, designers and SEO and marketing people. Followers as read on 29 September 2026.

Of the 32 without one, 31 have no {login}/{login} repository at all. One has the repository but no README file.

The 30 READMEs

Median length is 20.5 lines and 1,190 bytes. The longest is 202 lines. Length does not track audience in any useful way: the Spearman correlation between followers and line count is -0.06 across all 30, and 0.25 among the 19 top-followed accounts. Both are weak.

Pinned repositories are more common than READMEs. 37 of the 62 use all six pin slots, and 14 pin nothing. Of the 30 with a README, 22 pin six. Of the 32 without, 15 do. That is a correlation, not a cause.

What to do

Pin six repositories first. It is quick, and more accounts here use it than have a README.

Then, if you write a README, write about 20 lines. Say who you are and what you make in the first line. Link out to your site and one thing you built, and a few more if you have them: the median is 4 or 5 links.

The length and the link count come from the data. The first-line advice is mine. No opening is shared by most of the 30. The most common is a heading, at 13 of 30.

If you have nothing to show yet, skip the README. 25 of the 44 most-followed did.

What not to bother with

• A typing header. 0 of 30.
• A stats widget. 3 of 30, and none of the 22 accounts with a 1,000-star repo. The best-known widget tool is popular, but in this sample of top accounts it is rare.
• A badge wall. 7 of 30. I read the image URLs of those 7 by hand: 4 are mostly tech-stack icons, 2 are live follower or star counters, 1 is contact links.

Limits

n is small: 30 READMEs coded, 62 accounts checked for existence. The accounts are the most-followed, which is not the population of people starting out. For 22 of the 30, the most-starred repo has 1,000 stars or more, so the audience is likely to predate the README.

I have no data on whether a README changes what a visitor does. This describes what top accounts have, not what works.

The rules for "stats widget" and "badge wall" are mine. They look at image sources only, and a different badge threshold would change the wall count.

Method and rerun

For each account I requested GET /repos/{login}/{login}/readme and coded the returned text with fixed rules. The repository's method.md has the exact selection rule, every API call and every coding rule. Each README is stored as a size and a SHA-256 hash, not as text, so the CSV shows what was coded without republishing anyone's file.

python code_profiles.py    # regenerates data/profiles.csv
python summarize.py        # prints every number in the guide

Cite, and licence

Rish Sadh, "What top GitHub profile READMEs actually contain", 2026-09-29.

Text and data: CC BY 4.0. Scripts: MIT.