Skip to content

About

GitHub Wrapped: your GitHub year as an animated story. Contributions, streaks, languages, projects and your developer archetype. Read-only, privacy-first, open source.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

8 stars

Watchers

0 watching

Forks

Repository files navigation

WrapYourGit

Every green square has a story. Here's yours, in motion.

Your year of code: your GitHub year, played back as a short animated story with its own soundtrack:
contributions, streaks, the languages you lived in, the projects you built, and the kind of developer you turned out to be.

CI License: MIT Edition PRs welcome

Next.js Remotion TypeScript Tailwind CSS Bun PostgreSQL

Get your recap · How it works · Privacy · Report a bug · Request a feature


Cell, the WrapYourGit mascot, waving in front of snapshots of a workshop, fireworks and mountains
Table of contents

Why WrapYourGit

  • Numbers you can trust. Every metric has a written definition and a GitHub source in metrics.md. Your 2026 total matches the "contributions in 2026" on your profile. When GitHub doesn't provide something, the recap says unavailable instead of showing a misleading 0, and estimates are marked with "~".
  • A story, not a dashboard. Your year becomes a city with one building per day, and the camera flies through it stop by stop to a soundtrack: your busiest day, your rhythm, your languages, a comparison with last year, and a letter from Cell that reads your year the way a friend would. A quiet year is told it counts; a relentless one is told to rest.
  • Your private work counts. Contributions to private repositories, yours and your organisations', are in your total. Your public page and its card never name them; your own story and downloads show the names only if you choose to, and you can change that in Settings.
  • Anyone's year, by username. Type a GitHub username and its public recap plays, read with the server's own read-only token. Signing in adds your private contribution counts to your own.
  • Read-only, and yours to delete. Signing in asks GitHub for no repository permissions, the code is never read, and "Delete my data" removes everything, hides your public recap and revokes access.

back to top

The story, as a city

Your year becomes a city, one building per day. The camera stops at 14 places and waits for your tap, so you go at your own pace; the MP4 holds each stop for about three seconds instead. Nine of the stops:

Hello: Cell at the controls of a small green engine under a sign reading 2026, @octo-sample
1. Hello
Cell says hi
Your year as a city, seen from above: the rail winds past every station, 1,284 contributions
4. Your year as a city
One building per day
Your busiest day: a green tower with a number-one plate beside a calendar page for January 3
5. Your busiest day
The tallest building
Your rhythm: seven wagons loaded with crates, one per weekday
6. Your rhythm
Your weekdays, as a train
Languages: three blocks sized by share, TypeScript 42%, JavaScript 28%, Python 18%
7. Languages
A garden, weighted by what you committed
Projects: containers stacked by commits, private repositories unnamed
8. Projects
Where your commits went
Community: an observatory under a sky of stars, 128 stars earned and 12 forks
9. Community
Stars and forks
Your archetype: Builder, Cell in a hard hat in a city block where a building goes up
11. Your archetype
And why
The year in one frame: a party at the last stop, with 1,284 contributions, Builder beside a gold trophy and 186 active days
14. The year in one frame
Fireworks over the city

Frames from a recap built on sample data, not a real account.

back to top

What kind of developer were you?

The climax of the story names your archetype, with the facts that earned it. You get one, plus up to two runner-ups you came close to. If none fits yet, the story says so honestly.

Cell as the Builder: orange, in a hard hat, hammering in the workshop
Builder · orange, in a hard hat, hammering in the workshop
Created two or more repositories, or made 50+ commits to your own.
Cell as the Consistent one: green, in a sweatband, running laps on the track
Consistent · green, in a sweatband, running laps on the track
Active on at least 30% of the days so far.
Cell as the Explorer: sky blue, cap and backpack, waving from the mountains
Explorer · sky blue, cap and backpack, waving from the mountains
Wrote in four or more languages.
Cell as the Collaborator: pink, in a headset, handing work on over a shared map
Collaborator · pink, in a headset, handing work on over a shared map
Ten or more reviews, or ten or more pull requests to other people's repositories.
Cell as the Night owl: lavender, owl tufts and glasses, grooving over the city at night
Night owl · lavender, owl tufts and glasses, grooving over the city at night
40%+ of sampled commits between 22:00 and 04:00. Estimated, and labelled so.
Cell as the Open sourcer: teal, in a scarf, cheering by a community mural
Open sourcer · teal, in a scarf, cheering by a community mural
Contributed to three or more public repositories you don't own.

back to top

What you keep

🎬 The story Plays in your browser with its own soundtrack, stop by stop.
🖼️ Slides as PNG One 1080 × 1350 image per stop of the story, letter pages included, or all of them in a ZIP. Rendered in your own browser.
📄 One PDF The same slides in a single file, for keeping or printing.
🔗 A public page Every GitHub username has one at /<username>, built from public activity only. You can hide yours in Settings.
🪪 A share card A 1200 × 630 image for social posts, also used as the page's preview.
🎞️ An MP4 video In 9:16, 4:5, 1:1 and 16:9, with the soundtrack, rendered in your own browser.

The dashboard adds a profile-style overview: your calendar, highlights, languages, this year against the same span of last year, and the repositories that caught your eye.

Privacy by design

Cell asleep: private work stays private

  • What it reads: the counts GitHub keeps about your year (contributions, languages, repositories you committed to, stars, pull requests).
  • What it never touches: your code. Signing in asks for no repository permissions at all.
  • Where your token lives: on the server only, encrypted with AES-256-GCM. Never sent to your browser.
  • What goes public: a recap of your public GitHub activity at /<your-username>, like your profile. It never shows private repository names, your timezone or the hours you commit, and Settings has a switch to hide it.
  • How to leave: Settings → Delete my data removes everything and revokes WrapYourGit's access.

Full policy: wrapyourgit.com/privacy.


back to top

How it works

flowchart LR
  user([You]) -->|Sign in with GitHub| web[apps/web<br>Next.js]
  visitor([Anyone]) -->|types a username| web
  web -->|your token, or the public token,<br>server only| gh[packages/github<br>GraphQL queries]
  gh -->|raw activity| an[packages/analytics<br>pure functions]
  an -->|validated by packages/schema| rd[(RecapData<br>Postgres)]
  rd --> player[Story in the browser<br>Remotion Player]
  rd --> pub[Public recap at /username<br>public activity only]
  rd --> card[Share card]
  video[packages/video<br>Remotion scenes] --> player
  video --> exports[MP4 · PNG · ZIP · PDF<br>rendered in your browser]
Loading

One validated document, RecapData, is the contract between everything: GitHub data goes in once, and the same scenes play in the browser and render to video and slides there, so the numbers on screen and in the export never disagree. More in the architecture overview.

Tech stack

Area Tools
Web Next.js 16 (App Router, Cache Components), React 19, Tailwind CSS 4
Story and video Remotion 4, baked 3D art (animated WebP and stills, no WebGL in the browser), a synthesised CC0 soundtrack
Data GitHub GraphQL API, Zod 4 schemas, PostgreSQL with Drizzle ORM
Auth GitHub App user authorisation with PKCE, AES-256-GCM token encryption
Tooling Bun workspaces, TypeScript strict, Biome, bun test, GitHub Actions

Run it locally

Requires Bun 1.4+, Node 22+, and Docker or Podman for the database.

git clone https://github.com/habibiahmada/wrapyourgit.git
cd wrapyourgit
bun install
cp .env.example apps/web/.env.local     # fill in your GitHub App and database settings
bun scripts/dev-db.ts                   # Postgres on localhost:54329
bun run --filter @wyg/web db:migrate
bun run dev                             # http://localhost:3000

Just want to see the video? bun run studio opens Remotion Studio with sample data, no sign-in needed. The full guide, including creating your own GitHub App, is in docs/development/setup.md; running it on a server is in docs/deployment/guide.md.

Command What it does
bun run dev Web app on http://localhost:3000
bun run studio Remotion Studio with sample data
bun test Unit tests
bun run typecheck Strict TypeScript in every workspace
bun run lint Biome lint and format check (bun run format fixes)
bun run build Production build of the web app

Project structure

apps/
  web/          Next.js: landing, sign-in, dashboard, story, public pages, SEO
packages/
  schema/       RecapData zod schema and video formats: the contract
  github/       GitHub GraphQL client and queries
  analytics/    Pure functions from raw activity to RecapData, with tests
  video/        Remotion scenes, illustrations, soundtrack
scripts/        Data spike, local database, art and track generation, dev stills (lib/still.ts)
docs/           Product spec, metric definitions, ADRs, design, setup

Documentation

Read For
docs/analytics/metrics.md How every number is defined and where it comes from
docs/architecture/overview.md System shape, data flow, auth and sync
docs/architecture/decisions Architecture decision records
DESIGN.md Visual direction for the story, video and web
docs/video/scene-system.md Scenes, layouts, soundtrack and export
docs/product/prd.md · roadmap What we build, and when
AGENTS.md The short guide for contributors and AI coding agents

Roadmap

  • Sign in with GitHub, sync, dashboard and the nine-chapter story
  • Slides as PNG, ZIP and PDF; public page and share card
  • A recap for any GitHub username at /<username>, which its owner can hide
  • Comparison with last year; repositories you starred
  • The story as one continuous world with a moving camera (design)
  • MP4, slides and PDF rendered in your browser, in four aspect ratios
  • More soundtracks
  • Final 2026 recaps after the year ends

See the roadmap and changelog for detail.

Contributing

Contributions are welcome, from a wrong number you spotted to a new scene. Start with CONTRIBUTING.md, and please follow the Code of Conduct. Security issues go through SECURITY.md, never a public issue.

License and credits

WrapYourGit is released under the MIT License, © 2026 Habibi Ahmad Aziz.

Credit when you fork or modify it. The MIT License requires every copy, fork and modified version to keep the copyright notice and the license text; do not remove or replace them. If you fork, modify or deploy WrapYourGit, please also credit the original author in your README and, for a public deployment, where people can see it (a footer or an about page), for example:

Based on WrapYourGit by Habibi Ahmad Aziz

The NOTICE file says the same.

Its dependencies keep their own licences (third-party notices); notably Remotion is not MIT and needs a company licence for companies with more than three employees (remotion.dev/license).

  • Language logos from Devicon (MIT); the logos are trademarks of their owners.
  • The soundtrack is synthesised by scripts/synth-track.ts and released as CC0.
  • Fonts: Mona Sans and Bricolage Grotesque (SIL Open Font License).
  • Inspired by Spotify Wrapped and the open-source year-in-review projects before it, including GitHub Unwrapped by Remotion.

WrapYourGit is an independent project. It reads your activity through the public GitHub API; GitHub is a trademark of GitHub, Inc.

About

GitHub Wrapped: your GitHub year as an animated story. Contributions, streaks, languages, projects and your developer archetype. Read-only, privacy-first, open source.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

8 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages