Open-source project
srizzon/git-city avatar
srizzon/git-city

Git City renders every GitHub profile as a building you can fly past

Your GitHub profile as a 3D pixel art building in an interactive city

5,995 stars295 forksTypeScriptAGPL-3.0

At a glance

What is it?
Git City is a TypeScript app that turns GitHub profiles into a Three.js city of pixel art buildings. Here is how the building metrics work, what the local stack replaces, and what a fresh clone cannot give you.
Who is it for?
Git City suits anyone who wants their GitHub activity to read as a place instead of a chart, and the local Supabase path makes a first run possible without a remote project. Anyone hosting it publicly has to plan for the AGPL source disclosure, and anyone who wants new shop models needs the upload script, which is not in the repository.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • srizzon/git-city5,995 ★ · +206
Star history
Repository2026-09-232026-11-15
srizzon/git-city5.8k6k

206 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Height from contributions, width from repos, windows from stars

Every GitHub user in Git City becomes one building, and four numbers set its shape. Contributions drive height, so one thousand commits produce a taller tower. Public repos drive width, which widens the base. Stars set window brightness, and recent activity decides the window pattern, so an active account glows differently from a dormant one. Around that geometry sits an achievement system keyed to contributions, stars, repos and referrals, plus a shop that only opens once you claim your building. Claimed buildings take crowns, auras, roof effects and face decorations. The renderer uses instanced meshes with a level of detail system: close buildings animate their windows at full detail, distant buildings fall back to simplified geometry. Around the towers sit the social pieces, a live activity feed, kudos sent to other developers, gifted items, referrals, and a compare mode that puts two developers side by side. Share cards export the result as a landscape or stories image.

Every script passes --webpack while the stack page promises Turbopack

The stack page names Next.js 16 with the App Router and Turbopack, then every dev and build script in package.json opts back out of that bundler: dev runs `next dev -p 3001 --webpack` and build runs `next build --webpack`. The port is pinned to 3001 in three separate scripts, and the environment file sets NEXT_PUBLIC_BASE_URL to http://localhost:3001 to match. dev:prod loads `.env.prod` through dotenv, dev:staging loads `.env.dev`, and dev:portless wraps the same dev command in portless. Around those sit the everyday chores: `db:up` runs supabase migration up, `db:reset` runs supabase db reset, `lint` calls eslint, `test` runs vitest run, and formatting goes through prettier with both a write and a check mode. The package is named git-city at version 0.1.0 and marked private, so nothing is published to a registry, and the repository has no GitHub releases, so there is no changelog to read. The last push on the default branch main is dated 2026-10-26.

Sign in with GitHub falls back to a dev login that takes any username

Local sign-in cannot use the real provider. The GitHub OAuth app needs a client secret that cannot ship inside the repository, so on a local stack the Sign in with GitHub button lands on a built-in dev login instead: type any GitHub username, you are inside, and a building is created from that account. The same door sits at `/api/dev/login`, and that route is switched off automatically in production. A hosted Supabase project does the real authentication. You configure the GitHub OAuth provider, add your local callback URL if the setup requires it, and put a personal access token in `GITHUB_TOKEN` for the API calls. Fine-grained tokens are recommended over classic ones so you grant only the repository and profile access the app needs. Admin rights are split across two keys: `ADMIN_GITHUB_LOGINS` is a comma separated list of usernames checked server-side, and the browser only receives an isAdmin flag, while `ARCADE_ADMIN_KEY` is a bearer token for the admin room invalidate endpoint. The service role key also belongs in `.env.local`, so a local checkout ends up holding three long lived secrets.

Shop models come from an upload script that is kept out of git

Cosmetics need 3D models, and the repository does not include the step that produces them. `NEXT_PUBLIC_MODELS_BASE_URL` is left empty for local development, where the files are served from `/public/models/`. In production that variable is supposed to point at the Supabase Storage public URL for the cosmetic-models bucket, and the note beside it says the models are uploaded with scripts/upload-cosmetic-models.mjs, which is kept out of git. A fresh clone therefore gives you the shop interface, the empty base URL, and no way to fill the bucket. The arcade follows the same pattern: an empty `NEXT_PUBLIC_COZY_BASE_URL` means assets are served locally from `/public/cozy/`, while production expects the arcade-assets bucket on Supabase Storage. Multiplayer runs through a worker in party/ on Cloudflare, with `NEXT_PUBLIC_PARTYKIT_HOST` defaulting to localhost:1999 and a wrangler.jsonc file at the root. An optional token path is configured too, with GITC burned for Pixels and an in-city swap on Base using a Reown project id and an Alchemy key for browser RPC.

Clone, copy the env file, and the city renders on port 3001

The install path is short. Clone the repository, install dependencies, copy the example environment file to `.env.local`, fill in the values, and start the dev server.

bash
# Clone the repo
git clone https://github.com/srizzon/git-city.git
cd git-city

# Install dependencies
npm install

# Set up environment variables

# Linux / macOS
cp .env.example .env.local

# Windows (Command Prompt)
copy .env.example .env.local

# Windows (PowerShell)
Copy-Item .env.example .env.local

# Fill in your environment variables

# Run the dev server
npm run dev

Open `http://localhost:3001` and the city is there. A remote backend needs the three Supabase values from Project Settings -> API plus the GitHub token. For a backend with no remote project at all, the Supabase CLI route asks for a container runtime first, either Docker Desktop or Colima on macOS. After `supabase start` pulls images and prints a local URL and keys, `supabase status` prints them again, Studio runs at `http://127.0.0.1:54323`, `supabase db reset` re-applies every migration on a clean database, and `supabase stop` shuts the stack down with the data preserved.

An AGPL city with an MIT trailer kit and no written rollback

Two licenses live in one repository. The city itself is AGPL-3.0, so any public deployment must share the source code, while the trailer kit under `.claude/skills/gg/` is MIT and installs with `npx skills add srizzon/git-city --skill gg`, which means any web game can use it. That kit is a real engine feature rather than a mock-up: a film is a timeline of takes on the music's beat grid, a studio page plays it, and the export renders it frame by frame to an mp4 with synthesized music and sound effects, no samples involved. The films run at `/trailer/minimal`, `/trailer/demo` and `/trailer/towns`, driven by the `trailer:export` and `trailer:audio` scripts. What the README leaves out is the operational half. No rollback procedure is written down for the migration set, no refresh cadence is stated for rebuilding existing buildings from GitHub data, and with no releases published there is no upgrade path to follow.

Editorial conclusion

Git City suits anyone who wants their GitHub activity to read as a place instead of a chart, and the local Supabase path makes a first run possible without a remote project. Anyone hosting it publicly has to plan for the AGPL source disclosure, and anyone who wants new shop models needs the upload script, which is not in the repository. Check the port 3001 binding, the service role key sitting in your local env file, and the absent rollback notes before you build on it.

Frequently asked questions

What is Git City?

Git City turns every GitHub profile into a pixel art building inside an interactive 3D city. Building height follows contributions, width follows public repos, stars set window brightness, and recent activity shapes the window pattern. You can fly between buildings in free flight mode, open a profile page per developer, and compare two of them side by side.

In Git City's case, what does Git stand for?

Inside Git City the name points at GitHub account data. Each user becomes a building generated from contributions, public repos, stars and activity, with a dedicated profile page carrying stats, achievements and top repositories. The live site is at thegitcity.com and the app is hosted on Vercel.

What does "git" mean in urban slang when the project is called Git City?

The project's own documentation does not define the slang sense of the word. What it defines is a city where GitHub profiles become buildings, with achievements, a shop selling crowns, auras, roof effects and face decorations, social features such as kudos and gifts, and a multiplayer arcade backed by a worker in party/ on Cloudflare.

Where is Git City located?

Git City has no physical location. It is a Next.js app on Vercel with the live site at thegitcity.com. Locally the dev server binds to port 3001, the Supabase Studio database browser runs at `http://127.0.0.1:54323`, and the multiplayer host in NEXT_PUBLIC_PARTYKIT_HOST defaults to localhost:1999.

Official sources

  1. Issues
  2. License: AGPL-3.0
  3. Project website
  4. README
  5. srizzon/git-city on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/srizzon-git-city.svg)](https://hysenlabs.com/projects/srizzon-git-city)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/srizzon-git-city.svg)](https://hysenlabs.com/projects/srizzon-git-city)

Was this useful?