You’ve probably never thought about where your GitHub followers actually live. I didn’t either—until I built a tool that maps every single one of them onto a globe. What I saw made me rethink everything I believed about open source and remote work.
Let me back up. I’m a developer who spends most of my day staring at commits, pull requests, and issue threads. GitHub is the ultimate digital space—code doesn’t care where you are. It’s just text. So when I heard about a project called Gitcharta that transforms public GitHub profile data into an interactive map, I was skeptical. Why would anyone need to see where their followers are? I thought. Code is code. Location is irrelevant.
I was wrong.
The tool uses D3 and React to scrape follower locations from GitHub profiles and plot them on a world map. It’s simple. But the result is anything but. Within minutes, I saw clusters of dots glowing in San Francisco, New York, London, and Berlin. 80% of my followers came from five cities. The rest of the world? Barely a sprinkle.
That’s the moment the twist hit me: the internet is global, but open source is local. We’ve been sold a story that remote work and digital collaboration have flattened the world. But the data says otherwise. Geography didn’t die—it just went underground. And GitHub, the ultimate symbol of borderless code, is actually a map of where the tech talent physically lives.
I started digging into the source analysis. The creator, Thierry Rakotomanana, built a custom TypeScript geocoder to map raw user locations like ‘SF’ and ‘NYC’ to coordinates. That’s the hard part—turning messy text into a visual story. But the real insight is what happens when you zoom out. Open-source contribution is still heavily concentrated in a handful of geographic nodes. It’s not a decentralized utopia. It’s a network of hubs.
You might be thinking: So what? Who cares where my followers are? You should care if you’re a maintainer planning a meetup, a company trying to understand adoption, or a developer wondering why your docs get traction in one region and not another. This map gives you a tangible way to see your community’s global reach—and its blind spots. Need to translate your README into Spanish? Look at the map. Want to host a hackathon? Pick the city with the densest cluster.
But there’s a darker side too. If open source is so geographically concentrated, then ‘remote work’ is a privilege of the few. The people contributing to the most popular repos are overwhelmingly living in expensive tech hubs. That means the voices shaping the tools we all use are coming from a tiny slice of the planet. The diversity problem isn’t just about gender or race—it’s about zip codes.
I reached out to a friend who runs a large open-source project. He said: ‘I always assumed our community was global. Then I mapped our stargazers. Half of them are within a 50-mile radius of Silicon Valley.’ We thought we were building for everyone, but we were building for our neighbors.
This isn’t an indictment of GitHub or remote work. It’s a revelation. The most important thing you can do for your open-source project is to look at a map of your community. Not your commit history. Not your star count. The actual locations of the people who follow you. That’s where the real story lives.
FAQ
Q: Isn't this just a fun visualization? What's the real value?
A: The value goes beyond curiosity. For maintainers, it reveals where your actual community is concentrated, helping you decide where to host events, which languages to translate docs into, and how to target outreach. For companies, it shows whether your open-source adoption is truly global or just clustered in a few cities. It's a strategic tool hiding in a pretty map.
Q: Does this mean remote work is a failure?
A: No, but it shows that remote work hasn't automatically decentralized talent. Even in a 'location-agnostic' field like open source, contributors still cluster in a few geographic hubs—likely due to time zones, education, and network effects. The takeaway is that if you want a truly global community, you need to actively work against geographic gravity, not assume it will disappear.
Q: Couldn't the map be biased by GitHub's user base?
A: Yes, GitHub's user base skews toward developers in English-speaking, internet-connected regions. But that's exactly the point: the map exposes the existing bias. It's not a perfect representation of all open-source contributors, but it's a stark reminder of who is currently participating—and who is missing. The data is a mirror, not a map of the world.